Triple
T9836977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Outlaw |
E239125
|
entity |
| Predicate | costumeDesignEmphasisOn |
P90245
|
FINISHED |
| Object | Jane Russell’s figure |
—
|
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: Jane Russell’s figure | Statement: [The Outlaw, costumeDesignEmphasisOn, Jane Russell’s figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeDesignEmphasisOn Context triple: [The Outlaw, costumeDesignEmphasisOn, Jane Russell’s figure]
-
A.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
-
B.
costumeDesignerOfWork
Indicates that an entity serves as the costume designer responsible for the costumes in a particular creative work.
-
C.
costumeDesignStyle
Indicates the stylistic approach or aesthetic characteristics used in designing a costume for a character or production.
-
D.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
E.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb33b07688190b78a70cf535c3efc |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.