Triple
T16462873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugs’ White Water Rapids |
E399850
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Hopkins Rides |
E1142874
|
NE 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: Hopkins Rides | Statement: [Bugs’ White Water Rapids, manufacturer, Hopkins Rides]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hopkins Rides Context triple: [Bugs’ White Water Rapids, manufacturer, Hopkins Rides]
-
A.
Hopkins Rides
chosen
Hopkins Rides is an amusement ride manufacturer known for designing and building water rides and other attractions for theme parks.
-
B.
Hopkin
Hopkin is a surname and given name of English and Welsh origin, often considered a variant of Hopkins.
-
C.
TheRide
TheRide is the public transit system serving Ann Arbor and the surrounding Washtenaw County area in Michigan.
-
D.
Hopkins
Hopkins is a common English and Welsh surname borne by numerous notable figures across politics, the arts, and academia.
-
E.
Hopkins
Hopkins is a small suburban city in Minnesota located just west of Minneapolis.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d824cd881909b1f2fd40e14ee35 |
completed | April 18, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f555f6081908b1f0d524b6fb9a7 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:10 a.m.