Triple
T33428286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 2 (Metro-North Railroad) |
E856049
|
entity |
| Predicate | fareUsage |
P54839
|
FINISHED |
| Object | applies to one-way tickets |
—
|
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: applies to one-way tickets | Statement: [Zone 2 (Metro-North Railroad), fareUsage, applies to one-way tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareUsage Context triple: [Zone 2 (Metro-North Railroad), fareUsage, applies to one-way tickets]
-
A.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
-
B.
fareZoneUsage
chosen
Indicates how a fare zone is applied or utilized within a transportation or pricing context.
-
C.
fareContext
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
D.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
E.
tourUsage
Indicates how a tour is intended to be used or the manner in which it is utilized within a given context.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.