Triple
T2033137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Only the Paranoid Survive |
E44561
|
entity |
| Predicate | illustratesWith |
P202
|
FINISHED |
| Object | Intel memory-to-microprocessor transition |
—
|
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: Intel memory-to-microprocessor transition | Statement: [Only the Paranoid Survive, illustratesWith, Intel memory-to-microprocessor transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illustratesWith Context triple: [Only the Paranoid Survive, illustratesWith, Intel memory-to-microprocessor transition]
-
A.
hasIllustrationsBy
Indicates that one entity (such as a work or publication) includes illustrations that were created by another entity (the illustrator).
-
B.
hasIllustrations
Indicates that an entity includes or is accompanied by visual illustrations.
-
C.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
D.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
-
E.
demonstratedBy
chosen
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.