Triple
T8817056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 286 |
E209802
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | SR 7 |
E270127
|
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: SR 7 | Statement: [SR 286, connectsTo, SR 7]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 7 Context triple: [SR 286, connectsTo, SR 7]
-
A.
SR 7
chosen
SR 7 is a major east–west state highway in Virginia that connects the Washington, D.C. metropolitan area with communities in Northern Virginia and the Shenandoah Valley.
-
B.
SR 756
SR 756 is a Nevada state highway that serves as a short connector route in the western part of the state.
-
C.
SR 57
SR 57 is a state highway in Ohio that serves as a regional connector route through several communities in the northern part of the state.
-
D.
SR 27
SR 27 is a state highway in Maine that runs north–south, connecting coastal communities with inland towns and recreational areas.
-
E.
SR 27
SR 27 is a state highway in Georgia that runs east–west across the southeastern part of the state, connecting several small towns and regional routes.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600bd8a88190ad891a96201d796b |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fc1579c8190ade0f780183aa1dc |
completed | April 3, 2026, 7:44 a.m. |
Created at: March 30, 2026, 6:46 p.m.