Triple
T5753584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington City Park Carousel |
E126910
|
entity |
| Predicate | typicalRiders |
P51007
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [Burlington City Park Carousel, typicalRiders, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRiders Context triple: [Burlington City Park Carousel, typicalRiders, children]
-
A.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
B.
typicalRiderEmotion
Indicates the characteristic or commonly experienced emotion that a rider typically feels in the context of a particular riding situation or activity.
-
C.
isRiddenBy
Indicates that an entity serves as a mount or vehicle that is being ridden by another entity.
-
D.
ridershipLevel
Indicates the magnitude or intensity of usage by riders or passengers for a given service, route, or system.
-
E.
notableRiderType
chosen
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029032ba08190ae4062d74ab271ee |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.