Triple
T29648021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Law of Robotics |
E756056
|
entity |
| Predicate | hasHigherPriorityThan |
P13790
|
FINISHED |
| Object | robot self-preservation |
—
|
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: robot self-preservation | Statement: [First Law of Robotics, hasHigherPriorityThan, robot self-preservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherPriorityThan Context triple: [First Law of Robotics, hasHigherPriorityThan, robot self-preservation]
-
A.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
B.
hasLowerPrecedenceThan
Indicates that one item is ranked or ordered with a lower priority or importance compared to another item.
-
C.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
D.
isHigherThan
chosen
Indicates that one entity has a greater value, level, or position than another entity.
-
E.
hasPrecedence
Indicates that one entity occurs, is considered, or is applied before another in order, priority, or importance.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 6:50 p.m.