Triple
T2398589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Oman in Washington, D.C. |
E47707
|
entity |
| Predicate | hasHostCityStatus |
P37931
|
FINISHED |
| Object | capital city of the United States |
—
|
LITERAL FINISHED |
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: capital city of the United States | Statement: [Embassy of Oman in Washington, D.C., hasHostCityStatus, capital city of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostCityStatus Context triple: [Embassy of Oman in Washington, D.C., hasHostCityStatus, capital city of the United States]
-
A.
hasHostCity
Indicates that a particular event, organization, or activity is located in or officially hosted by a specific city.
-
B.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
-
C.
inauguralHostCity
Indicates the city that first hosted a particular event, competition, or series.
-
D.
longtimeHostCity
Indicates that a city has hosted a particular event or activity repeatedly over an extended period of time.
-
E.
hasParticipantCity
Indicates that a city is involved as a participant in an event, activity, or relationship.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c798248190a41bb08d9148f009 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc664317c8190a6bb5a5065c21bde |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.