Triple
T33771483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poppy Land |
E865392
|
entity |
| Predicate | hasSetDesignStyle |
P198964
|
FINISHED |
| Object | elaborate themed compound |
—
|
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: elaborate themed compound | Statement: [Poppy Land, hasSetDesignStyle, elaborate themed compound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetDesignStyle Context triple: [Poppy Land, hasSetDesignStyle, elaborate themed compound]
-
A.
hasSetDesign
chosen
Indicates that something possesses or is associated with a particular set design, typically defining the visual or physical layout of a scene or environment.
-
B.
hasDesignProperty
Indicates that an entity possesses a specific design-related characteristic, feature, or attribute.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
usesSetDesignFrom
Indicates that one production or work employs the same set design that was originally created for another production or work.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 1, 2026, 1:45 a.m.