Triple
T23868330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagner Company |
E592650
|
entity |
| Predicate | dismissesCharacter |
P154253
|
FINISHED |
| Object | Willy Loman |
—
|
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: Willy Loman | Statement: [Wagner Company, dismissesCharacter, Willy Loman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dismissesCharacter Context triple: [Wagner Company, dismissesCharacter, Willy Loman]
-
A.
removedCharacter
Indicates that a character was taken out or deleted from a text, sequence, or collection.
-
B.
declineCharacterization
Indicates that an entity rejects or refuses a particular description, label, or portrayal applied to it.
-
C.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
D.
karakter
Indicates that one entity is a character (e.g., a role or persona) associated with or embodied by another entity.
-
E.
treatsCharacter
Indicates how one character behaves toward or interacts with another character, especially in terms of care, respect, or mistreatment.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae548dc8190a5f84f2cd7f9778e |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:14 p.m.