Triple
T10962085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrio Mágico Turístico de la Ciudad de México |
E258999
|
entity |
| Predicate | typeOfStatus |
P96867
|
FINISHED |
| Object | honorary designation |
—
|
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: honorary designation | Statement: [Barrio Mágico Turístico de la Ciudad de México, typeOfStatus, honorary designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStatus Context triple: [Barrio Mágico Turístico de la Ciudad de México, typeOfStatus, honorary designation]
-
A.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
B.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- F. None of above. chosen
Provenance (4 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7712bf65c8190b847784d885876fd |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.