Triple
T37617804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back Alley Oproar |
E935975
|
entity |
| Predicate | featuresHumanCharacter |
P206008
|
FINISHED |
| Object | Elmer Fudd |
E58831
|
NE 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: Elmer Fudd | Statement: [Back Alley Oproar, featuresHumanCharacter, Elmer Fudd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHumanCharacter Context triple: [Back Alley Oproar, featuresHumanCharacter, Elmer Fudd]
-
A.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
B.
featuresReturningCharacterFrom
Indicates that a work includes the reappearance of a character who previously appeared in the referenced source work.
-
C.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
AICharacteristics
Indicates the defining traits, behaviors, or properties that characterize an artificial intelligence system.
-
E.
featuresCharacterAction
Indicates that a work includes a specific action performed by a particular character.
- F. None of above. chosen
Provenance (5 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdab674c81908a047785e8aaafa7 |
completed | June 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.