Triple
T1596754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound City |
E34298
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Gateway City |
E34568
|
NE 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: Gateway City | Statement: [Mound City, relatedTo, Gateway City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gateway City Context triple: [Mound City, relatedTo, Gateway City]
-
A.
Gateway City
chosen
Gateway City is a nickname for St. Louis, Missouri, highlighting its historic role as a major entry point to the American West.
-
B.
River City
River City is a popular nickname for Sacramento, California, highlighting the city’s close connection to the nearby American and Sacramento Rivers.
-
C.
River City
River City is a popular nickname for Wuhan, a major central Chinese metropolis known for its location at the confluence of the Yangtze and Han rivers.
-
D.
River City
River City is a popular nickname for Richmond, Virginia, highlighting the city's location along the James River and its historic riverfront character.
-
E.
Gate City
Gate City is a commonly used nickname for Greensboro, North Carolina, reflecting its historic role as a major transportation and commercial hub.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9092e46748190b27be7d1aba07dff |
completed | March 5, 2026, 4:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51b9c6588190810ede38d9e714e2 |
completed | March 8, 2026, 10:38 a.m. |
Created at: March 4, 2026, 7:27 p.m.