Triple
T3416915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop |
E72030
|
entity |
| Predicate | fareStructureFeature |
P49336
|
FINISHED |
| Object | stored value |
—
|
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: stored value | Statement: [Hop, fareStructureFeature, stored value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareStructureFeature Context triple: [Hop, fareStructureFeature, stored value]
-
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.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
C.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
D.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
E.
fareTypes
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.