Triple
T34888451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Zone 8 |
E1006213
|
entity |
| Predicate | fareStructureComponent |
P108836
|
FINISHED |
| Object | base rail fare |
—
|
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: base rail fare | Statement: [Amtrak Zone 8, fareStructureComponent, base rail fare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareStructureComponent Context triple: [Amtrak Zone 8, fareStructureComponent, base rail fare]
-
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.
fareStructureFeature
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
-
C.
feeComponents
Indicates that a fee is composed of one or more sub-fees or cost elements that together make up the total charge.
-
D.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
E.
partOfFareStructure
chosen
Indicates that one element is included as a component within a larger fare structure or pricing scheme.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.