Triple
T18585565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flat fare (Washington Metro) |
E454227
|
entity |
| Predicate | fareIntegrationContext |
P51453
|
FINISHED |
| Object | WMATA regional fare policies |
—
|
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: WMATA regional fare policies | Statement: [flat fare (Washington Metro), fareIntegrationContext, WMATA regional fare policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareIntegrationContext Context triple: [flat fare (Washington Metro), fareIntegrationContext, WMATA regional fare policies]
-
A.
fareIntegrationScope
chosen
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.
fareContext
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
D.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
E.
fareSystemPreviously
Indicates that a particular fare system existed or was in use at an earlier time relative to another fare system or time period.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b0dff08190a3be481faec34a3c |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.