Triple
T27466584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania–New Jersey state line |
E693190
|
entity |
| Predicate | crossedByRailLine |
P416
|
FINISHED |
| Object | Northeast Corridor |
—
|
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: Northeast Corridor | Statement: [Pennsylvania–New Jersey state line, crossedByRailLine, Northeast Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedByRailLine Context triple: [Pennsylvania–New Jersey state line, crossedByRailLine, Northeast Corridor]
-
A.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
B.
railCrossingBetween
Indicates that a railway crossing is located between two specified entities or locations, connecting or intersecting them.
-
C.
hasRailwayCrossing
Indicates that a location or route includes a point where a railway line and a road or path intersect, typically at the same level.
-
D.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
E.
crossedByTunnel
Indicates that one entity (typically a barrier like a mountain, river, or road) is traversed or passed through by another entity via a tunnel.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 12:52 p.m.