Triple
T29185751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbie |
E739863
|
entity |
| Predicate | lawInConflict |
P92949
|
FINISHED |
| Object | First Law of Robotics |
—
|
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: First Law of Robotics | Statement: [Herbie, lawInConflict, First Law of Robotics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawInConflict Context triple: [Herbie, lawInConflict, First Law of Robotics]
-
A.
legalDoctrineChallenged
Indicates that a particular legal doctrine is being disputed, questioned, or contested, typically through litigation or formal legal argument.
-
B.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
C.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
D.
conflictWithLaw
chosen
Indicates that an action, situation, or entity violates, contradicts, or is incompatible with a law or legal regulation.
-
E.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:59 a.m.