Triple
T35044069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIRR Main Line trains |
E1011147
|
entity |
| Predicate | primaryCorridorBetween |
—
|
GENERATED |
| Object | New York City |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCorridorBetween Context triple: [LIRR Main Line trains, primaryCorridorBetween, New York City]
-
A.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
B.
parallelTransportCorridor
Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
-
C.
isMainCorridor
Indicates that a corridor serves as the primary or central passageway within a building or structure.
-
D.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
E.
primaryRouteThrough
chosen
Indicates that one location or path serves as the main or most significant route passing through another location or area.
- F. None of above.
Provenance (1 batch)
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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.