Triple
T29599135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Law of Robotics |
E754391
|
entity |
| Predicate | hasPriorityRank |
P17947
|
FINISHED |
| Object | third |
—
|
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: third | Statement: [Third Law of Robotics, hasPriorityRank, third]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriorityRank Context triple: [Third Law of Robotics, hasPriorityRank, third]
-
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.
hasGovernancePriority
Indicates that a particular issue, objective, or domain is assigned a specified level of importance or precedence within a governance framework or decision-making process.
-
C.
hasPriorityGroup
Indicates that one entity is assigned to, or associated with, a specific priority group relative to others.
-
D.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
E.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: April 28, 2026, 6:20 p.m.