Triple
T34669146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-Spec |
E890330
|
entity |
| Predicate | cameraOptions |
P20442
|
FINISHED |
| Object | cockpit view (in supported titles) |
—
|
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: cockpit view (in supported titles) | Statement: [A-Spec, cameraOptions, cockpit view (in supported titles)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraOptions Context triple: [A-Spec, cameraOptions, cockpit view (in supported titles)]
-
A.
cameraConfiguration
Indicates the specific setup or arrangement of a camera’s parameters or components in a given context.
-
B.
cameraStyle
chosen
Indicates the characteristic visual approach or technique used by a camera in capturing or presenting imagery.
-
C.
cameraOperator
Indicates that one entity operates, controls, or is responsible for handling the camera for another entity or production.
-
D.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
E.
cameraSystem
Indicates a relationship where an entity functions as or is part of a camera-based monitoring or imaging system.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722fa31248190a1c9081ce8cfa37b |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.