Triple
T14462322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZHP |
E358612
|
entity |
| Predicate | fareSystemContext |
P106903
|
FINISHED |
| Object | London fare system |
—
|
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: London fare system | Statement: [ZHP, fareSystemContext, London fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareSystemContext Context triple: [ZHP, fareSystemContext, London fare system]
-
A.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
B.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
-
C.
fareSystemFeature
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
D.
fareContext
chosen
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
E.
fareSystemChange
Indicates a change in the rules, structure, or method by which fares are calculated, collected, or applied.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.