Triple
T35469805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Horrible |
E1025175
|
entity |
| Predicate | aspiresToJoin |
P178518
|
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, aspiresToJoin, Evil League of Evil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aspiresToJoin Context triple: [Dr. Horrible, aspiresToJoin, Evil League of Evil]
-
A.
aspiredTo
Indicates that one entity had a strong desire or ambition to achieve, become, or obtain the other entity.
-
B.
joinsTeamAs
Indicates that one entity becomes a member of a team in a specified role or capacity.
-
C.
canJoin
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
-
D.
aimsToForm
Indicates an intention or effort by one entity to create, establish, or bring about a particular relationship, structure, or outcome with another entity.
-
E.
seeksToBe
chosen
Indicates an entity’s intention or effort to become or attain the state, role, or condition represented by another 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.