Triple
T38477277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortex shrinks the Earth |
E915580
|
entity |
| Predicate | hasVillainPlanType |
P195887
|
FINISHED |
| Object | worldDomination |
—
|
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: worldDomination | Statement: [Cortex shrinks the Earth, hasVillainPlanType, worldDomination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillainPlanType Context triple: [Cortex shrinks the Earth, hasVillainPlanType, worldDomination]
-
A.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
B.
isTypeOfVillain
Indicates that one entity is classified as a particular type or category of villain in relation to another entity.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
hasVillainFactionClasses
Indicates that certain classes or categories are associated with, or belong to, a villainous faction.
-
E.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.