Triple
T14533257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoky Mountain River Rampage |
E340967
|
entity |
| Predicate | seatingCapacityPerRaft |
P2491
|
FINISHED |
| Object | 6 riders |
—
|
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: 6 riders | Statement: [Smoky Mountain River Rampage, seatingCapacityPerRaft, 6 riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityPerRaft Context triple: [Smoky Mountain River Rampage, seatingCapacityPerRaft, 6 riders]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
C.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
D.
capacityPerChair
Indicates the amount of capacity (such as weight, volume, or occupancy) that is assigned to or supported by each individual chair.
-
E.
capacityPerSide
Indicates the maximum quantity or volume that each individual side or unit in a pair can hold or accommodate.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea053f9bc8190901b9d321811d881 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.