Triple
T21440224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 18 (NJ Transit) |
E528918
|
entity |
| Predicate | fareTableInclusion |
P143952
|
FINISHED |
| Object | NJ Transit rail fare charts |
—
|
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: NJ Transit rail fare charts | Statement: [Zone 18 (NJ Transit), fareTableInclusion, NJ Transit rail fare charts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareTableInclusion Context triple: [Zone 18 (NJ Transit), fareTableInclusion, NJ Transit rail fare charts]
-
A.
fareIncludes
Indicates that a given fare covers or contains specific components, services, or conditions as part of its overall offering.
-
B.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
C.
farePolicySupport
Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
-
D.
farePolicyRelatedTo
Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
-
E.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 6:05 p.m.