Triple
T2133518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventureland |
E46596
|
entity |
| Predicate | intendedExperience |
P22360
|
FINISHED |
| Object | sense of exploration |
—
|
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: sense of exploration | Statement: [Adventureland, intendedExperience, sense of exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedExperience Context triple: [Adventureland, intendedExperience, sense of exploration]
-
A.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
B.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
C.
primaryExperience
chosen
Indicates that one entity is the main or most significant experience associated with another entity, as opposed to secondary or supporting experiences.
-
D.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
E.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba0c42c8190ab3ce4bbf1531ee1 |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.