Triple
T8494627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positronic brain |
E201065
|
entity |
| Predicate | hasFictionalCapability |
P58963
|
FINISHED |
| Object | fast logical computation |
—
|
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: fast logical computation | Statement: [positronic brain, hasFictionalCapability, fast logical computation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalCapability Context triple: [positronic brain, hasFictionalCapability, fast logical computation]
-
A.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
B.
hasFictionalProperty
chosen
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
-
C.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
D.
fictionalAbilitySource
Indicates that a fictional character’s abilities originate from, or are powered by, a specified source.
-
E.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
- 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.