Triple
T31841880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministerio de Asuntos Exteriores, Unión Europea y Cooperación |
E812831
|
entity |
| Predicate | sedeEn |
P162988
|
FINISHED |
| Object | Madrid |
—
|
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: Madrid | Statement: [Ministerio de Asuntos Exteriores, Unión Europea y Cooperación, sedeEn, Madrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sedeEn Context triple: [Ministerio de Asuntos Exteriores, Unión Europea y Cooperación, sedeEn, Madrid]
-
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.
alsoSeatOf
Indicates that a location serves as an additional or alternative seat (e.g., of government, administration, or authority) alongside another primary seat.
-
D.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
E.
hasHindquartersOf
Indicates that one entity possesses or exhibits the hindquarters characteristic or form of another entity.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6affbdda88190a9f53dc2550ca324 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:49 p.m.