Triple
T619729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvin the Paranoid Android |
E14484
|
entity |
| Predicate | hasIntelligenceLevel |
P11340
|
FINISHED |
| Object | planet-sized 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: planet-sized brain | Statement: [Marvin the Paranoid Android, hasIntelligenceLevel, planet-sized brain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntelligenceLevel Context triple: [Marvin the Paranoid Android, hasIntelligenceLevel, planet-sized brain]
-
A.
intelligenceLevel
chosen
Indicates the degree or measure of cognitive ability or intelligence attributed to an entity.
-
B.
hasCognitiveComponent
Indicates that the related entity or process involves or depends on mental activities such as thinking, reasoning, perception, or understanding.
-
C.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
E.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e270b448190beb677670443b5b6 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.