Triple
T323365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Metro |
E6462
|
entity |
| Predicate | annualRidership |
P11438
|
FINISHED |
| Object | over 2 billion passengers |
—
|
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: over 2 billion passengers | Statement: [Moscow Metro, annualRidership, over 2 billion passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualRidership Context triple: [Moscow Metro, annualRidership, over 2 billion passengers]
-
A.
dailyRidership
Indicates the typical number of people who use or ride a given transportation service each day.
-
B.
dailyRidershipPeak
Indicates that the relationship specifies the highest number of riders or users recorded for a service or system within a single day.
-
C.
hasApproxAnnualPassengerUsageRank
Indicates the approximate position or ranking of an entity based on its annual passenger usage compared to similar entities.
-
D.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
E.
passengerTrafficRankUS
Indicates the relative ranking of a location or facility within the United States based on the volume of passenger traffic it handles.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.