Triple
T1760342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden State Parkway |
E38642
|
entity |
| Predicate | runsNorthSouth |
P11673
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Garden State Parkway, runsNorthSouth, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsNorthSouth Context triple: [Garden State Parkway, runsNorthSouth, true]
-
A.
northSouthRoutes
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
B.
runsDirection
chosen
Indicates that an entity moves or operates in a specified direction.
-
C.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
D.
northSection
Indicates that one entity is located in, belongs to, or corresponds to the northern section or northern part of another entity.
-
E.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.