Triple
T38450914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotlight (cinematography) |
E912171
|
entity |
| Predicate | framingFocus |
P31
|
FINISHED |
| Object | group dynamics |
—
|
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: group dynamics | Statement: [Spotlight (cinematography), framingFocus, group dynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: framingFocus Context triple: [Spotlight (cinematography), framingFocus, group dynamics]
-
A.
framed
Indicates that one entity has been falsely presented or set up to appear responsible or guilty for an action or situation, typically to mislead others.
-
B.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
focusMode
Indicates that an entity is currently in a concentrated or distraction-minimized state directed toward a specific task, target, or context.
-
E.
structureFocus
Indicates that attention or emphasis is placed on the structural aspects or organization of something within the described context.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.