Triple
T14741967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eureka Mountain Mine Ride |
E346369
|
entity |
| Predicate | hadThemeElement |
P115587
|
FINISHED |
| Object | animatronic miners |
—
|
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: animatronic miners | Statement: [Eureka Mountain Mine Ride, hadThemeElement, animatronic miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadThemeElement Context triple: [Eureka Mountain Mine Ride, hadThemeElement, animatronic miners]
-
A.
hasThemeInStory
Indicates that a particular theme is present or plays a significant role within a given story.
-
B.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
C.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
D.
performedThemeFor
Indicates that an agent carried out or executed a performance specifically for a particular theme or subject.
-
E.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.