Triple
T8494637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positronic brain |
E201065
|
entity |
| Predicate | governsEntity |
P760
|
FINISHED |
| Object | behavior of Asimovian robots |
—
|
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: behavior of Asimovian robots | Statement: [positronic brain, governsEntity, behavior of Asimovian robots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsEntity Context triple: [positronic brain, governsEntity, behavior of Asimovian robots]
-
A.
governedEntity
Indicates that one entity exercises authority, control, or governance over another entity.
-
B.
governingEntityName
Indicates the name of the organization, body, or authority that governs, manages, or has official control over the referenced entity.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.