Triple
T30957779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRIF |
E788723
|
entity |
| Predicate | headquartersAdministrativeRegion |
P100332
|
FINISHED |
| Object | Capitale-Nationale |
—
|
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: Capitale-Nationale | Statement: [MRIF, headquartersAdministrativeRegion, Capitale-Nationale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersAdministrativeRegion Context triple: [MRIF, headquartersAdministrativeRegion, Capitale-Nationale]
-
A.
headquartersAdministrativeTerritory
chosen
Indicates that an entity serves as the administrative headquarters or seat of government for a specified territory or jurisdiction.
-
B.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
-
C.
headquartersTerritory
Indicates the territory or region in which an entity’s main headquarters is located.
-
D.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
-
E.
headquartersDistrict
Indicates the administrative district or area where an organization’s main headquarters is located.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.