Triple
T34258376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-13 |
E878956
|
entity |
| Predicate | parallelToHighway |
P56524
|
FINISHED |
| Object | I-75 |
—
|
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: I-75 | Statement: [M-13, parallelToHighway, I-75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelToHighway Context triple: [M-13, parallelToHighway, I-75]
-
A.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
followsHighway
chosen
Indicates that one entity’s path or route runs along, parallels, or adheres closely to the course of a specified highway.
-
C.
positionOnHighway
Indicates that one entity’s location is specified relative to a particular highway, such as being on, along, or at a point on that highway.
-
D.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
E.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:56 a.m.