Triple
T1760378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden State Parkway |
E38642
|
entity |
| Predicate | hasRestArea |
P29828
|
FINISHED |
| Object | various service plazas with fuel and food |
—
|
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: various service plazas with fuel and food | Statement: [Garden State Parkway, hasRestArea, various service plazas with fuel and food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestArea Context triple: [Garden State Parkway, hasRestArea, various service plazas with fuel and food]
-
A.
hasRestAreas
chosen
Indicates that a route, location, or facility includes one or more designated rest areas available for use.
-
B.
hasDropOffArea
Indicates that an entity provides a designated area where items, passengers, or goods can be temporarily left or unloaded.
-
C.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
-
D.
hasRestrooms
Indicates that a place or facility provides access to restroom or toilet amenities.
-
E.
hasParkArea
Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
- 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.