Triple
T22919865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur – In the Minimoys Kingdom |
E568830
|
entity |
| Predicate | indoorComponent |
P150259
|
FINISHED |
| Object | dark ride scenes |
—
|
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: dark ride scenes | Statement: [Arthur – In the Minimoys Kingdom, indoorComponent, dark ride scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorComponent Context triple: [Arthur – In the Minimoys Kingdom, indoorComponent, dark ride scenes]
-
A.
indoorTitle
Indicates that an entity holds a title, role, or designation specifically applicable within an indoor context or indoor environment.
-
B.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
C.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
D.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
E.
indoorSport
Indicates that the sport or physical activity is typically played or practiced indoors rather than outdoors.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d40f98819096210c097b47d43b |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.