Triple
T26918176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killmotor Hill |
E677568
|
entity |
| Predicate | universeCreator |
P27680
|
FINISHED |
| Object | The Walt Disney Company |
—
|
NE NERFINISHED |
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: The Walt Disney Company | Statement: [Killmotor Hill, universeCreator, The Walt Disney Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeCreator Context triple: [Killmotor Hill, universeCreator, The Walt Disney Company]
-
A.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
B.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
C.
creatorOfUniverse
chosen
Indicates that an entity is responsible for bringing the universe into existence or causing its creation.
-
D.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
E.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 6:05 a.m.