Triple
T9672588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 214 (unused number) |
E234064
|
entity |
| Predicate | adjacentNumbersInclude |
P89545
|
FINISHED |
| Object | Interstate 210 |
unclear NED1
|
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: Interstate 210 | Statement: [Interstate 214 (unused number), adjacentNumbersInclude, Interstate 210]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentNumbersInclude Context triple: [Interstate 214 (unused number), adjacentNumbersInclude, Interstate 210]
-
A.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
B.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
C.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
D.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
E.
hasAdjacentRole
Indicates that one role is positioned directly next to or alongside another role within a defined structure or sequence.
- F. None of above. chosen
Provenance (5 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a83e3a616a48190973075731965b9ce |
completed | Aug. 18, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.