Triple
T37315057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instituto de Salud para el Bienestar |
E926310
|
entity |
| Predicate | tiene sede en |
P162988
|
FINISHED |
| Object | Ciudad de México |
—
|
NE NERFINISHED |
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: Ciudad de México | Statement: [Instituto de Salud para el Bienestar, tiene sede en, Ciudad de México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiene sede en Context triple: [Instituto de Salud para el Bienestar, tiene sede en, Ciudad de México]
-
A.
tieneSedePrincipal
chosen
Indicates that an entity has its main headquarters or principal office located in a specified place.
-
B.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
C.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
D.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
-
E.
hasSeatOfAdministration
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:16 p.m.