Triple
T20315816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megatrain |
E510376
|
entity |
| Predicate | fareCondition |
P51767
|
FINISHED |
| Object | limited availability |
—
|
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: limited availability | Statement: [Megatrain, fareCondition, limited availability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareCondition Context triple: [Megatrain, fareCondition, limited availability]
-
A.
fareStatus
chosen
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
-
B.
fareContext
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
C.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
D.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
E.
fareProblem
Indicates that there is an issue, dispute, or irregularity related to the fare charged or paid for a trip or service.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.