Triple
T31357861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Humanoids |
E799784
|
entity |
| Predicate | robotPrimeDirective |
P171663
|
FINISHED |
| Object | To Serve and Obey, And Guard Men From Harm |
—
|
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: To Serve and Obey, And Guard Men From Harm | Statement: [The Humanoids, robotPrimeDirective, To Serve and Obey, And Guard Men From Harm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotPrimeDirective Context triple: [The Humanoids, robotPrimeDirective, To Serve and Obey, And Guard Men From Harm]
-
A.
robotFunction
Indicates the specific role, task, or operational purpose that a robot is designed or configured to perform.
-
B.
robotType
Indicates the specific category or kind of robot that an entity belongs to.
-
C.
robotFeature
Indicates that a robot possesses or is characterized by a particular feature or attribute.
-
D.
mainRobotCharacter
Indicates that the referenced entity is the primary robot protagonist or central robotic figure in a narrative or scenario.
-
E.
roleAtUSRobots
Indicates that an entity holds or held a specific role or position at the organization US Robots.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:17 p.m.