Triple
T34672779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weasel (DC Extended Universe) |
E890419
|
entity |
| Predicate | costumePerformedBy |
P173050
|
FINISHED |
| Object | Sean Gunn |
—
|
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: Sean Gunn | Statement: [Weasel (DC Extended Universe), costumePerformedBy, Sean Gunn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumePerformedBy Context triple: [Weasel (DC Extended Universe), costumePerformedBy, Sean Gunn]
-
A.
costumeDesignerOfWork
Indicates that an entity serves as the costume designer responsible for the costumes in a particular creative work.
-
B.
isCostumedCharacterFor
Indicates that one entity serves as a costumed character representation or mascot for another entity, typically for promotional or entertainment purposes.
-
C.
wornByActor
chosen
Indicates that a wearable item (such as clothing or accessories) is being worn by a particular actor.
-
D.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
-
E.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232166488190939c02bdaeacb490 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.