Triple
T36465887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Metro unified zone |
E898419
|
entity |
| Predicate | distanceCharging |
P204882
|
FINISHED |
| Object | no distance-based surcharge within zone |
—
|
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: no distance-based surcharge within zone | Statement: [Moscow Metro unified zone, distanceCharging, no distance-based surcharge within zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceCharging Context triple: [Moscow Metro unified zone, distanceCharging, no distance-based surcharge within zone]
-
A.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
-
B.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
-
C.
chargingZone
Indicates a designated area or zone where charging (typically of vehicles or devices) is permitted or intended to occur.
-
D.
electricCharging
Indicates the action or process of supplying electrical energy to charge a device, vehicle, or battery.
-
E.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.