Triple
T2317511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East River Tunnels |
E51098
|
entity |
| Predicate | carriedTrafficType |
P27830
|
FINISHED |
| Object | passenger trains |
—
|
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: passenger trains | Statement: [East River Tunnels, carriedTrafficType, passenger trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedTrafficType Context triple: [East River Tunnels, carriedTrafficType, passenger trains]
-
A.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
B.
hasCargoTrafficType
Indicates that an entity is associated with a specific type or category of cargo traffic it handles or supports.
-
C.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
D.
servesPassengerTrafficType
chosen
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
E.
hasTrafficPattern
Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.