Triple
T30766315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partner at White Horse Pictures |
E783380
|
entity |
| Predicate | decisionPowerOver |
P34807
|
FINISHED |
| Object | slate selection |
—
|
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: slate selection | Statement: [Partner at White Horse Pictures, decisionPowerOver, slate selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionPowerOver Context triple: [Partner at White Horse Pictures, decisionPowerOver, slate selection]
-
A.
deFactoPowerOver
Indicates a situation where one entity effectively controls or dominates another in practice, even without formal or legally recognized authority.
-
B.
hasDecisionMakingPower
chosen
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
C.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
-
D.
hasNoPowerOver
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
E.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:40 p.m.