Triple
T31695827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARTM A |
E808914
|
entity |
| Predicate | fareIntegrationRole |
P171225
|
FINISHED |
| Object | core zone for integrated 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: core zone for integrated fares | Statement: [ARTM A, fareIntegrationRole, core zone for integrated fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareIntegrationRole Context triple: [ARTM A, fareIntegrationRole, core zone for integrated fares]
-
A.
fareIntegrationScope
Indicates the extent to which fares are coordinated or unified across different transportation services or systems.
-
B.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
-
C.
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.
-
D.
fareGroupingRole
chosen
Indicates the role or function an entity has within a specific fare grouping or fare structure.
-
E.
fareIntegrator
Indicates a relationship where one system or entity combines, coordinates, or manages fare information or payments across multiple sources or services.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:10 p.m.