Triple
T18231645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robot Monster |
E436555
|
entity |
| Predicate | portraysCharacter |
P1668
|
FINISHED |
| Object | Ro-Man |
—
|
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: Ro-Man | Statement: [Robot Monster, portraysCharacter, Ro-Man]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ro-Man Context triple: [Robot Monster, portraysCharacter, Ro-Man]
-
A.
Ro-Man
chosen
Ro-Man is the gorilla-suited, helmeted alien robot villain from the 1953 cult science-fiction film "Robot Monster."
-
B.
Overman
Overman is a surname of English origin borne by various notable individuals, including actors and public figures.
-
C.
Romek
Romek is a common Polish diminutive form of the male given name Roman.
-
D.
Roh
Roh is the ancestral figure or eponym from whom the Rohilla people derive their name and historical identity.
-
E.
Robotman
Robotman is a DC Comics superhero and core member of the Doom Patrol, a former race car driver whose brain was transplanted into a powerful robotic body after a near-fatal accident.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b3495881909f2a3f3a8db43792 |
completed | April 19, 2026, 3:28 p.m. |
Created at: April 10, 2026, 10:33 a.m.