Triple
T17149733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasy Forest |
E416188
|
entity |
| Predicate | rideRestrictionFocus |
P114807
|
FINISHED |
| Object | younger guests |
—
|
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: younger guests | Statement: [Fantasy Forest, rideRestrictionFocus, younger guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideRestrictionFocus Context triple: [Fantasy Forest, rideRestrictionFocus, younger guests]
-
A.
rideRestriction
chosen
Indicates that there is a limitation or rule governing whether, how, or under what conditions one entity may ride or be transported by another.
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
rideStyle
Indicates the manner or characteristic way in which an entity rides or is ridden (e.g., in terms of technique, comfort, or behavior).
-
D.
transportRestriction
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
E.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4067470819084aa233c4c4a6d4f |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.