Triple
T5741029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musical Ride |
E126613
|
entity |
| Predicate | numberOfRiders |
P65583
|
FINISHED |
| Object | 32 |
—
|
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: 32 | Statement: [Musical Ride, numberOfRiders, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRiders Context triple: [Musical Ride, numberOfRiders, 32]
-
A.
numberOfRidersPerVehicle
Indicates the quantity of riders associated with each individual vehicle in the relationship.
-
B.
ridersPerRow
Indicates the number of riders assigned or allowed to sit in each row.
-
C.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
D.
ridershipLevel
Indicates the magnitude or intensity of usage by riders or passengers for a given service, route, or system.
-
E.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0258382908190af8787feb1e5fbcd |
completed | March 22, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c022a50c048190aff24c63e7039dd6 |
completed | March 22, 2026, 5:11 p.m. |
Created at: March 22, 2026, 3:48 p.m.