Triple
T31438786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul Metrobus |
E802010
|
entity |
| Predicate | approximateDailyRidership |
P10158
|
FINISHED |
| Object | hundreds of thousands of 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: hundreds of thousands of passengers | Statement: [Istanbul Metrobus, approximateDailyRidership, hundreds of thousands of passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDailyRidership Context triple: [Istanbul Metrobus, approximateDailyRidership, hundreds of thousands of passengers]
-
A.
annualRidership
Indicates the total number of passengers who use a transportation service over the course of one year.
-
B.
dailyRidership
chosen
Indicates the typical number of people who use or ride a given transportation service each day.
-
C.
dailyRidershipPeak
Indicates that the relationship specifies the highest number of riders or users recorded for a service or system within a single day.
-
D.
dailyRidershipCategory
Indicates the classification of an entity based on the typical number of riders it serves per day.
-
E.
peakDailyTrains
Indicates the maximum number of trains operating per day on a given route, line, or segment during its busiest period.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 30, 2026, 9:04 p.m.