Triple
T23553986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VBB fare system |
E578127
|
entity |
| Predicate | hasConcessionaryFaresFor |
P119588
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [VBB fare system, hasConcessionaryFaresFor, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcessionaryFaresFor Context triple: [VBB fare system, hasConcessionaryFaresFor, children]
-
A.
hasTollConcession
Indicates that an entity has been granted the right or authorization to collect tolls for the use of a specific infrastructure or service.
-
B.
hasConcessions
Indicates that one entity provides or contains concession facilities, services, or rights (such as food, drink, or merchandise sales) for another entity or within a given context.
-
C.
supportsTransitDiscounts
chosen
Indicates that an entity provides or enables discounted fares or pricing for public transit services.
-
D.
usesSingleFareStructure
Indicates that the same fare rules and pricing structure are applied uniformly across all relevant services or routes.
-
E.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed17fc881908b45dcde14790d42 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.