Triple
T17973437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Willingham |
E449402
|
entity |
| Predicate | hasRoleInElementals |
P129962
|
FINISHED |
| Object | writer |
—
|
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: writer | Statement: [Bill Willingham, hasRoleInElementals, writer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInElementals Context triple: [Bill Willingham, hasRoleInElementals, writer]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
C.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
D.
elementalPower
Indicates a relationship where an entity possesses, controls, or is associated with a specific elemental force or power.
-
E.
hasSpiritSymbolRole
Indicates that an entity serves in a designated role or function specifically associated with a spirit symbol.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fca04481908f0dd875953fd82f |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.