Triple
T37714814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warlock |
E939429
|
entity |
| Predicate | distinctiveTrait |
P128575
|
FINISHED |
| Object | refuses to kill to survive |
—
|
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: refuses to kill to survive | Statement: [Warlock, distinctiveTrait, refuses to kill to survive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctiveTrait Context triple: [Warlock, distinctiveTrait, refuses to kill to survive]
-
A.
distinguishingTrait
chosen
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
B.
iconicTrait
Indicates that a trait is emblematic or strongly characteristic of an entity, making it widely recognized as a defining feature of that entity.
-
C.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
-
D.
notableTraitInFiction
Indicates that a particular trait, characteristic, or quality is especially prominent or defining for an entity within fictional works.
-
E.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.