Triple
T5965278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opelika |
E132736
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Auburn, Alabama |
E98092
|
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: Auburn, Alabama | Statement: [Opelika, near, Auburn, Alabama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Auburn, Alabama Context triple: [Opelika, near, Auburn, Alabama]
-
A.
Auburn, Georgia
Auburn, Georgia is a small city in Barrow and Gwinnett counties within the Atlanta metropolitan area.
-
B.
Auburn
chosen
Auburn is a city in eastern Alabama known for being home to Auburn University and its strong college-town atmosphere.
-
C.
Auburn
Auburn is a suburban city in Washington State located south of Seattle, known for its residential communities, industrial areas, and regional transportation links.
-
D.
Auburn
Auburn is a historic Gold Rush-era city in California’s Sierra Nevada foothills, known for its preserved Old Town and role in the state’s mining heritage.
-
E.
Auburn
Auburn is a residential neighborhood located within the city of Cranston, Rhode Island.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03a3ca1dc819098cde8ae5ec1d845 |
completed | March 22, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113585ad88190a35d549448b10def |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:03 p.m.