Triple
T21440217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 18 (NJ Transit) |
E528918
|
entity |
| Predicate | fareStructureBasis |
P49336
|
FINISHED |
| Object | origin–destination zone pairs |
—
|
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: origin–destination zone pairs | Statement: [Zone 18 (NJ Transit), fareStructureBasis, origin–destination zone pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareStructureBasis Context triple: [Zone 18 (NJ Transit), fareStructureBasis, origin–destination zone pairs]
-
A.
fareStructure
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
B.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
C.
fareStructureFeature
chosen
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
-
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.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b700237c8190bbcb4bedc4242719 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6:05 p.m.