Triple
T29120722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spacers |
E737173
|
entity |
| Predicate | robotPolicy |
P85599
|
FINISHED |
| Object | widespread acceptance of robots in daily life |
—
|
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: widespread acceptance of robots in daily life | Statement: [Spacers, robotPolicy, widespread acceptance of robots in daily life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotPolicy Context triple: [Spacers, robotPolicy, widespread acceptance of robots in daily life]
-
A.
hasRobotPolicy
chosen
Indicates that an entity has an established policy governing the behavior, use, or management of robots.
-
B.
planningPolicy
Indicates that one entity establishes or defines rules, guidelines, or strategies governing how another entity should plan or make planning-related decisions.
-
C.
robotLawContext
Indicates the legal, ethical, or regulatory framework within which a robot’s actions, rights, or obligations are defined or evaluated.
-
D.
robotType
Indicates the specific category or kind of robot that an entity belongs to.
-
E.
walkingPolicy
Indicates the rules or guidelines that govern how walking is allowed, managed, or restricted in a given context.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:25 a.m.