Triple
T35469671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Horrible |
E1025172
|
entity |
| Predicate | organizationDesired |
P193154
|
FINISHED |
| Object | Evil League of Evil |
—
|
NE NERFINISHED |
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: Evil League of Evil | Statement: [Dr. Horrible, organizationDesired, Evil League of Evil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationDesired Context triple: [Dr. Horrible, organizationDesired, Evil League of Evil]
-
A.
organizationDescribedBy
Indicates that an organization is characterized, detailed, or explained by a particular description or document.
-
B.
organizationDirected
Indicates that one organization exercises authoritative control or guidance over another organization or its activities.
-
C.
organOrganization
Indicates that an organ is structurally or functionally part of, or associated with, a specific organization or organizational system.
-
D.
organizationFocus
Indicates the primary area of activity, mission, or specialization that an organization is oriented toward or concentrated on.
-
E.
organizationLed
Indicates that one organization provides leadership, direction, or governance over another organization or collective effort.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:04 p.m.