Triple
T17784414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Quintet of the Astonished |
E443979
|
entity |
| Predicate | cameraFraming |
P18585
|
FINISHED |
| Object | tight group portrait |
—
|
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: tight group portrait | Statement: [The Quintet of the Astonished, cameraFraming, tight group portrait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraFraming Context triple: [The Quintet of the Astonished, cameraFraming, tight group portrait]
-
A.
cameraConfiguration
Indicates the specific setup or arrangement of a camera’s parameters or components in a given context.
-
B.
frontCameraFeature
Indicates that an entity has a specified feature, capability, or characteristic associated with its front-facing camera.
-
C.
meetsInCamera
chosen
Indicates that two or more entities are physically present together in the same camera frame or shot at the same time.
-
D.
cameraStyle
Indicates the characteristic visual approach or technique used by a camera in capturing or presenting imagery.
-
E.
typicalCameraPlacement
Indicates the usual or standard spatial position where a camera is placed relative to a scene or subject.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48791dec0819090d6e88449389fc0 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.