Triple
T35172797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 69E |
E1015591
|
entity |
| Predicate | hasSpurRelationTo |
P3377
|
FINISHED |
| Object | Interstate 69 |
—
|
NE NERFINISHED |
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 69 | Statement: [Interstate 69E, hasSpurRelationTo, Interstate 69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpurRelationTo Context triple: [Interstate 69E, hasSpurRelationTo, Interstate 69]
-
A.
isSpurOf
chosen
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary entity.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
hasExternalRelationship
Indicates that an entity maintains a relationship or connection with another entity that lies outside its own immediate system, organization, or defined boundary.
-
D.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
E.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
- F. None of above.
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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:02 p.m.