Triple
T16956010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of America Roval 400 |
E411302
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Concord |
E405416
|
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: Concord | Statement: [Bank of America Roval 400, city, Concord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Concord Context triple: [Bank of America Roval 400, city, Concord]
-
A.
Concord
Concord is a suburban neighbourhood within the city of Vaughan in Ontario, Canada, known for its mix of industrial, commercial, and residential areas.
-
B.
Concord
chosen
Concord is the capital city of the U.S. state of New Hampshire, known for its historic role in American politics and its location along the Merrimack River.
-
C.
Concord
Concord is a residential and commercial district within the town of Washington in Tyne and Wear, England.
-
D.
Concord
Concord is the Roman goddess personifying harmony and agreement, especially in social and political relationships.
-
E.
Concord
Concord is a small town in Pike County, Georgia, known for its rural character and tight-knit community.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01bb700819082a441c124be3cb6 |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0148201f7c8190a964723ca7ef2b68 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:31 a.m.