Triple
T32707758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asymmetrical Productions |
E836318
|
entity |
| Predicate | creativeControlEmphasis |
P17414
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Asymmetrical Productions, creativeControlEmphasis, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeControlEmphasis Context triple: [Asymmetrical Productions, creativeControlEmphasis, high]
-
A.
effectEmphasis
Indicates that one entity highlights, intensifies, or draws special attention to the effect produced by another entity or action.
-
B.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
C.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
D.
emphasizesAbility
Indicates that one entity highlights, stresses, or draws special attention to the capability or skill of another entity.
-
E.
emphasizesPowerOver
Indicates a relationship where one entity highlights, prioritizes, or asserts dominance, control, or authority over another.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:10 a.m.