Triple
T4351833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Taxi |
E98043
|
entity |
| Predicate | fareRegulation |
P44689
|
FINISHED |
| Object | government-regulated fares |
—
|
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: government-regulated fares | Statement: [Dubai Taxi, fareRegulation, government-regulated fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareRegulation Context triple: [Dubai Taxi, fareRegulation, government-regulated fares]
-
A.
farePolicyAuthority
chosen
Indicates that an authority or organization is responsible for defining, regulating, or overseeing the fare policy applied to a transportation service or route.
-
B.
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.
-
C.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
D.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
E.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.