Triple
T6923516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centro Histórico de Guadalajara |
E160245
|
entity |
| Predicate | foundedAsUrbanCore |
P16032
|
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: [Centro Histórico de Guadalajara, foundedAsUrbanCore, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsUrbanCore Context triple: [Centro Histórico de Guadalajara, foundedAsUrbanCore, 16th century]
-
A.
foundedAsMetropolis
Indicates that an entity was originally established or designated as a metropolis, typically a major or principal city.
-
B.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
D.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
E.
isDowntownCoreOf
chosen
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fea8d08190b6099a24fbac7de5 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.