Triple
T31617263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men from Shiloh |
E806793
|
entity |
| Predicate | featuresMoreContemporaryCostumeDesign |
P90245
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Men from Shiloh, featuresMoreContemporaryCostumeDesign, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMoreContemporaryCostumeDesign Context triple: [The Men from Shiloh, featuresMoreContemporaryCostumeDesign, yes]
-
A.
costumeDesignStyle
Indicates the stylistic approach or aesthetic characteristics used in designing a costume for a character or production.
-
B.
costumeDesignEmphasisOn
chosen
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
C.
costumeInspiration
Indicates that one entity serves as the creative source or model for another entity’s costume design.
-
D.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
-
E.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a008c77d4dc8190b342d7407eaf48fa |
completed | May 10, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_6a008c18531c8190bbe883b73e6d023f |
completed | May 10, 2026, 1:46 p.m. |
Created at: April 30, 2026, 10:39 p.m.