Triple
T34487579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pedro |
E885370
|
entity |
| Predicate | usedInToponymicPattern |
P20238
|
FINISHED |
| Object | Spanish saint-based place names |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Spanish saint-based place names | Statement: [San Pedro, usedInToponymicPattern, Spanish saint-based place names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInToponymicPattern Context triple: [San Pedro, usedInToponymicPattern, Spanish saint-based place names]
-
A.
hasToponymicUse
chosen
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
B.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
C.
hasToponymicPattern
Indicates that there is a characteristic naming pattern or structure in place names associated with the entity.
-
D.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 2:01 a.m.