Triple
T32602401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Belgium in The Hague |
E833409
|
entity |
| Predicate | capitalOfReceivingState |
P71239
|
FINISHED |
| Object | The Hague |
—
|
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: The Hague | Statement: [Embassy of Belgium in The Hague, capitalOfReceivingState, The Hague]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfReceivingState Context triple: [Embassy of Belgium in The Hague, capitalOfReceivingState, The Hague]
-
A.
capitalOfAwardingState
Indicates that a location is the capital city of the state that granted or conferred a particular award.
-
B.
capitalOfNewState
Indicates that a city serves as the official capital of a newly established or newly recognized state.
-
C.
capitalCityOfAssociatedState
chosen
Indicates that a city serves as the capital of the state with which another entity is associated.
-
D.
hasCapitalOfContainingState
Indicates that a capital city is the official capital of a state that geographically contains a given area or entity.
-
E.
capitalOfDefeatedState
Indicates that one entity is the capital city of a state that has been defeated, typically in a conflict or war.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 1:05 a.m.