Triple
T33413819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robot Monster |
E855657
|
entity |
| Predicate | featuredCreature |
P83317
|
FINISHED |
| Object | alien gorilla-like monster |
—
|
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: alien gorilla-like monster | Statement: [Robot Monster, featuredCreature, alien gorilla-like monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCreature Context triple: [Robot Monster, featuredCreature, alien gorilla-like monster]
-
A.
mentionsCreature
Indicates that one entity refers to or brings up a particular creature in some form of communication or content.
-
B.
fictionalCreatureInteractedWithOnScreen
Indicates that a fictional creature and another entity are shown directly interacting with each other within an on-screen visual medium.
-
C.
featuresCreatureOrLegend
chosen
Indicates that something includes, depicts, or prominently involves a particular creature or legendary being.
-
D.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
E.
usesCreature
Indicates that one entity employs, controls, or relies on a creature to perform an action or fulfill a function.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: May 1, 2026, 1:36 a.m.