Triple
T23640909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey City–Atlantic City |
E583886
|
entity |
| Predicate | intraStateRoute |
P6309
|
FINISHED |
| Object | New Jersey |
—
|
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 | Statement: [Jersey City–Atlantic City, intraStateRoute, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intraStateRoute Context triple: [Jersey City–Atlantic City, intraStateRoute, New Jersey]
-
A.
adjacentStateRoute
Indicates that one state route is directly next to or shares a boundary or junction with another state route.
-
B.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
servedByStateRoute
Indicates that a location, facility, or area is provided access or transportation service by a particular state route.
-
D.
stateRouteConnection
Indicates a relationship where a state-level route connects or links two locations or transportation segments.
-
E.
SPRINTERRoute
Indicates that one entity is the route or path taken by a sprinter during a sprinting activity.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2808d888190a2198f5efd25f2df |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.