Triple
T17576951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newark North Gate railway station |
E428093
|
entity |
| Predicate | distanceToNewarkCastleStation |
P128073
|
FINISHED |
| Object | approximately 0.7 miles |
—
|
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: approximately 0.7 miles | Statement: [Newark North Gate railway station, distanceToNewarkCastleStation, approximately 0.7 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNewarkCastleStation Context triple: [Newark North Gate railway station, distanceToNewarkCastleStation, approximately 0.7 miles]
-
A.
distanceToNewarkNewJersey
Indicates the spatial distance between a given entity’s location and Newark, New Jersey.
-
B.
distanceFromPennStation
Indicates the physical distance between a given location and Penn Station.
-
C.
distanceFromHobokenTerminal
Indicates the measured distance between a given location and Hoboken Terminal.
-
D.
distanceToNewarkLibertyInternationalAirport
Indicates the measured distance between a given location and Newark Liberty International Airport.
-
E.
distanceToNewarkOnTrent
Indicates the measured distance between a given place or object and the location of Newark-on-Trent.
- F. None of above. chosen
Provenance (4 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463ca76848190a7beb6deb4b0f1a4 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.