Triple
T10559816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJ 518 |
E249184
|
entity |
| Predicate | routeNumberSuccessor |
P89539
|
FINISHED |
| Object | NJ 519 |
—
|
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: NJ 519 | Statement: [NJ 518, routeNumberSuccessor, NJ 519]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNumberSuccessor Context triple: [NJ 518, routeNumberSuccessor, NJ 519]
-
A.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
majorSuccessorRoute
chosen
Indicates that one route is the primary or main successor to another route in a sequence or network of routes.
-
C.
successorLocation
Indicates that one location directly follows or comes after another in a defined spatial or ordered sequence.
-
D.
successorStation
Indicates that one station directly follows another in a sequence, such as along a transit line or route.
-
E.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271f3c6c819080b49fbe3aa09e09 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.