Triple
T22706330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic center of Potosí |
E561461
|
entity |
| Predicate | foundedAsPartOfCity |
P2612
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [historic center of Potosí, foundedAsPartOfCity, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsPartOfCity Context triple: [historic center of Potosí, foundedAsPartOfCity, 16th century]
-
A.
locatedInCityFoundedFor
Indicates that something is located in a city that was specifically founded for that thing or for its primary purpose.
-
B.
foundedAsPartOf
chosen
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
C.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
D.
foundedAsResidenceOf
Indicates that something was originally established or created to serve as the residence of a particular person or group.
-
E.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178ceba6c8190a538366a8e4648de |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.