Triple
T17176540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Center of San Salvador |
E416874
|
entity |
| Predicate | foundedAsCityCenterInCentury |
P55571
|
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 San Salvador, foundedAsCityCenterInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCityCenterInCentury Context triple: [Historic Center of San Salvador, foundedAsCityCenterInCentury, 16th century]
-
A.
cityFoundedAround
chosen
Indicates that a city was established approximately at, but not exactly on, a specified time or period.
-
B.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
C.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
-
D.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
E.
locatedInCityFoundedFor
Indicates that something is located in a city that was specifically founded for that thing or for its primary purpose.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0e14e08190901b1fbccc9322ae |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.