Triple
T9004623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple ProRAW |
E215112
|
entity |
| Predicate | captureMode |
P21736
|
FINISHED |
| Object | still photography |
—
|
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: still photography | Statement: [Apple ProRAW, captureMode, still photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureMode Context triple: [Apple ProRAW, captureMode, still photography]
-
A.
captureType
chosen
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
-
B.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
-
C.
captures
Indicates that one entity seizes, traps, or takes control of another entity, often preventing its escape or freedom.
-
D.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc695afa34819086cf6fcce2997b5f |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.