Triple
T10857898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London public transport network |
E256316
|
entity |
| Predicate | dailyPassengerJourneys |
P10158
|
FINISHED |
| Object | millions |
—
|
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: millions | Statement: [London public transport network, dailyPassengerJourneys, millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyPassengerJourneys Context triple: [London public transport network, dailyPassengerJourneys, millions]
-
A.
dailyRidershipCategory
Indicates the classification of an entity based on the typical number of riders it serves per day.
-
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.
annualRidership
Indicates the total number of passengers who use a transportation service over the course of one year.
-
E.
hasDailyPassengerTraffic
Indicates the number of passengers that regularly use or pass through something (such as a station or route) each day.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.