Triple
T31485722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippines–United States border |
E803269
|
entity |
| Predicate | governingCountry2Capital |
P201308
|
FINISHED |
| Object | Washington, D.C. |
—
|
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: Washington, D.C. | Statement: [Philippines–United States border, governingCountry2Capital, Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCountry2Capital Context triple: [Philippines–United States border, governingCountry2Capital, Washington, D.C.]
-
A.
associatedCountryCapital
Indicates that a country is related to, or paired with, its capital city.
-
B.
countryCapitalLocatedWithin
Indicates that the capital city of a country is geographically situated within the boundaries of that country.
-
C.
homeCountryCapital
Indicates that a given city is the capital of a specified country that serves as an entity’s home or origin.
-
D.
countryCapitalRelation
Indicates that one entity is the capital city of the country represented by the other entity.
-
E.
countryCapitalLocatedIn
Indicates that the capital city of a country is geographically situated within that country.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
| PDg | Predicate description generation | batch_69ffe8eb47d48190acf7794ebe3ef4b8 |
completed | May 10, 2026, 2:09 a.m. |
Created at: April 30, 2026, 9:35 p.m.