Triple
T4565185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohyah & Ohno Drop Slides |
E121890
|
entity |
| Predicate | experienceFeature |
P57711
|
FINISHED |
| Object | sudden vertical-style drop |
—
|
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: sudden vertical-style drop | Statement: [Ohyah & Ohno Drop Slides, experienceFeature, sudden vertical-style drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experienceFeature Context triple: [Ohyah & Ohno Drop Slides, experienceFeature, sudden vertical-style drop]
-
A.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
B.
featuresExperiment
Indicates that an entity is involved in, or is the subject of, a specific experimental setup, test, or trial.
-
C.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
D.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
E.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.