Triple
T30686280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City–Fort Worth |
E781193
|
entity |
| Predicate | connectsCapitalCityOfState |
P35272
|
FINISHED |
| Object | Oklahoma |
—
|
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: Oklahoma | Statement: [Oklahoma City–Fort Worth, connectsCapitalCityOfState, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCapitalCityOfState Context triple: [Oklahoma City–Fort Worth, connectsCapitalCityOfState, Oklahoma]
-
A.
connectsCapitalOfState
Indicates a relationship where an entity is linked to the capital city of a given state.
-
B.
connectsCapitalCity
chosen
Indicates a relationship where an entity is linked or associated specifically with a capital city.
-
C.
connectsCapitalCityOf
Indicates a relationship where something links or provides a direct connection to the capital city of a specified region, country, or administrative entity.
-
D.
stateCapitalConnection
Indicates a relationship where one entity is the capital city of a given state or is otherwise connected to that state in its role as capital.
-
E.
connectsCapitalsOf
Indicates a relationship where something serves as a link or route between the capital cities of two regions or countries.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 8:33 p.m.