Triple
T14686420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domestic Airport railway station |
E344918
|
entity |
| Predicate | fareSurchargeApplies |
P115322
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Domestic Airport railway station, fareSurchargeApplies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareSurchargeApplies Context triple: [Domestic Airport railway station, fareSurchargeApplies, yes]
-
A.
fareSurchargeAppliesAt
Indicates that an additional fare or surcharge is in effect at a specified time, location, or under certain conditions.
-
B.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
C.
fareRequired
Indicates that a payment or fare is required for access to or use of a service, route, or transportation option.
-
D.
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.
-
E.
fareCapping
Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58306548190b981956a83a84b95 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.