Triple
T34968624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 78 in New Jersey |
E1008472
|
entity |
| Predicate | hasTollComponent |
P3376
|
FINISHED |
| Object | New Jersey Turnpike Newark Bay Extension |
—
|
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: New Jersey Turnpike Newark Bay Extension | Statement: [Interstate 78 in New Jersey, hasTollComponent, New Jersey Turnpike Newark Bay Extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTollComponent Context triple: [Interstate 78 in New Jersey, hasTollComponent, New Jersey Turnpike Newark Bay Extension]
-
A.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
B.
hasTollSegment
chosen
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
C.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
-
D.
hasTollAgency
Indicates that a transportation facility or route is operated, managed, or overseen by a specific toll-collecting agency.
-
E.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4 p.m.