Triple
T17973435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Willingham |
E449402
|
entity |
| Predicate | hasRoleInFables |
P90599
|
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, hasRoleInFables, writer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInFables Context triple: [Bill Willingham, hasRoleInFables, writer]
-
A.
roleInLegendarium
chosen
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
B.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
C.
hasNotableFable
Indicates that an entity is associated with a well-known or significant fable, either as its subject, source, or key element.
-
D.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
- 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_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. |
Created at: April 10, 2026, 10:22 a.m.