Triple
T19620098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 36 (Shenzhen Metro) |
E470980
|
entity |
| Predicate | hasCurrencyOfFares |
P136733
|
FINISHED |
| Object | Chinese yuan |
—
|
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: Chinese yuan | Statement: [Line 36 (Shenzhen Metro), hasCurrencyOfFares, Chinese yuan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyOfFares Context triple: [Line 36 (Shenzhen Metro), hasCurrencyOfFares, Chinese yuan]
-
A.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
B.
fareSurchargeApplies
Indicates that an additional charge is applied on top of the standard fare for a given trip or service.
-
C.
fareSurchargeAppliesAt
Indicates that an additional fare or surcharge is in effect at a specified time, location, or under certain conditions.
-
D.
comparedToOtherFares
Indicates a comparison relationship between one fare and other available fares, typically in terms of price, conditions, or benefits.
-
E.
hasPrestoFares
Indicates that an entity offers or supports fare payment using the Presto card system.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e512d08190a76bf81b3282e0e5 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:43 p.m.