Triple
T10245924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Evil |
E240211
|
entity |
| Predicate | notablePlan |
P93174
|
FINISHED |
| Object | hold the world ransom |
—
|
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: hold the world ransom | Statement: [Dr. Evil, notablePlan, hold the world ransom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlan Context triple: [Dr. Evil, notablePlan, hold the world ransom]
-
A.
notableBoard
Indicates that an entity serves on, or is significantly associated with, a board that is notable or of particular importance.
-
B.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableProposition
Indicates that a subject is associated with a proposition, statement, or claim that is considered notable or significant in some context.
-
E.
notableReport
Indicates that an entity has produced, authored, or is otherwise associated with a report that is considered notable or significant.
- F. None of above. chosen
Provenance (4 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d32741888190928b045e2241cfac |
completed | April 7, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:26 a.m.