Triple
T21024632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL zone C |
E517906
|
entity |
| Predicate | farePolicyAspect |
P142505
|
FINISHED |
| Object | distance-based zoning |
—
|
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: distance-based zoning | Statement: [SL zone C, farePolicyAspect, distance-based zoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePolicyAspect Context triple: [SL zone C, farePolicyAspect, distance-based zoning]
-
A.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
-
B.
farePolicyRelatedTo
Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
-
C.
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.
-
D.
farePolicyAuthority
Indicates that an authority or organization is responsible for defining, regulating, or overseeing the fare policy applied to a transportation service or route.
-
E.
farePolicyRole
Indicates the role or function an entity has within a fare policy, such as how it participates in defining, applying, or managing that policy.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc6059908190bf5c9ef9c30f1a32 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:55 p.m.