Triple
T15514361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fury of the Nile |
E368794
|
entity |
| Predicate | intendedRiderExperience |
P118952
|
FINISHED |
| Object | family thrill |
—
|
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: family thrill | Statement: [Fury of the Nile, intendedRiderExperience, family thrill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRiderExperience Context triple: [Fury of the Nile, intendedRiderExperience, family thrill]
-
A.
ridershipLevel
Indicates the magnitude or intensity of usage by riders or passengers for a given service, route, or system.
-
B.
hasRideExperience
Indicates that one entity has undergone, participated in, or possesses experience with a particular ride or riding activity in relation to another entity.
-
C.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
D.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
E.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:02 a.m.