Triple
T8579582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. Daneel Olivaw |
E203133
|
entity |
| Predicate | hasBrainType |
P18468
|
FINISHED |
| Object | positronic brain |
—
|
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: positronic brain | Statement: [R. Daneel Olivaw, hasBrainType, positronic brain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrainType Context triple: [R. Daneel Olivaw, hasBrainType, positronic brain]
-
A.
brain
Indicates that an entity functions as the brain (central cognitive or control organ) of another entity.
-
B.
hasCognitiveComponent
Indicates that the related entity or process involves or depends on mental activities such as thinking, reasoning, perception, or understanding.
-
C.
typeOfIntelligence
chosen
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
D.
hasAssociatedBrainRegions
Indicates that certain brain regions are functionally, structurally, or conceptually linked to a given entity or process.
-
E.
hasAI
Indicates that one entity possesses, incorporates, or is equipped with an artificial intelligence system.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea9a0708819084cb8b8d84017864 |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.