Triple
T9794708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Serve Man |
E237689
|
entity |
| Predicate | mainAlienCharacter |
P90011
|
FINISHED |
| Object | Kanamit ambassador |
—
|
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: Kanamit ambassador | Statement: [To Serve Man, mainAlienCharacter, Kanamit ambassador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAlienCharacter Context triple: [To Serve Man, mainAlienCharacter, Kanamit ambassador]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
mainRobotCharacter
Indicates that the referenced entity is the primary robot protagonist or central robotic figure in a narrative or scenario.
-
C.
mainThemeCharacter
Indicates that a character serves as the central or primary figure associated with the main theme of a work or narrative.
-
D.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
E.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34916dc8190acef2ba003e56a33 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:28 p.m.