Triple
T24929007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARRI RAW |
E618935
|
entity |
| Predicate | positionInWorkflow |
P79168
|
FINISHED |
| Object | camera acquisition stage |
—
|
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: camera acquisition stage | Statement: [ARRI RAW, positionInWorkflow, camera acquisition stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInWorkflow Context triple: [ARRI RAW, positionInWorkflow, camera acquisition stage]
-
A.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
B.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
C.
positionInPlan
chosen
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
D.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
E.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 5:29 a.m.