Triple
T25140623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Gatsby (stage productions) |
E629790
|
entity |
| Predicate | typicalCostumeStyle |
P60977
|
FINISHED |
| Object | 1920s fashion |
—
|
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: 1920s fashion | Statement: [The Great Gatsby (stage productions), typicalCostumeStyle, 1920s fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCostumeStyle Context triple: [The Great Gatsby (stage productions), typicalCostumeStyle, 1920s fashion]
-
A.
typicalCostumePattern
Indicates that one entity is the characteristic or commonly used costume pattern associated with another entity.
-
B.
costumeType
Indicates the specific kind or category of costume associated with an entity.
-
C.
costumeDesignStyle
chosen
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.
costumeInspiration
Indicates that one entity serves as the creative source or model for another entity’s costume design.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 18, 2026, 6:29 a.m.