Triple
T13784780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-485 |
E331225
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | I-485 |
E331225
|
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: I-485 | Statement: [I-485, abbreviation, I-485]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-485 Context triple: [I-485, abbreviation, I-485]
-
A.
I-485
chosen
I-485 is the beltway interstate highway that loops around the city of Charlotte, North Carolina.
-
B.
I-220
I-220 is an auxiliary Interstate Highway in the United States that serves as a bypass or loop around a primary Interstate route.
-
C.
I-229
I-229 is a short auxiliary Interstate Highway in Missouri that serves as a bypass and business route around downtown St. Joseph.
-
D.
I-229
I-229 is an auxiliary Interstate Highway that serves as a bypass route around Sioux Falls in southeastern South Dakota.
-
E.
I-520
I-520 is an auxiliary Interstate Highway that forms a partial beltway around Augusta, Georgia and North Augusta, South Carolina.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b07b0b2881909b316e3cc67f1ec1 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 10:11 p.m.