Triple
T20996393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Lyndon |
E517159
|
entity |
| Predicate | cameraLenses |
P41556
|
FINISHED |
| Object | specially modified NASA Zeiss lenses |
—
|
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: specially modified NASA Zeiss lenses | Statement: [Barry Lyndon, cameraLenses, specially modified NASA Zeiss lenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraLenses Context triple: [Barry Lyndon, cameraLenses, specially modified NASA Zeiss lenses]
-
A.
lensType
Indicates the specific kind or category of lens associated with or used by an entity.
-
B.
cameraLensType
chosen
Indicates the specific type or category of lens used or associated with a camera.
-
C.
laterLensType
Indicates that one lens type occurs or is used at a later time than another lens type in a temporal sequence.
-
D.
supportsInterchangeableLenses
Indicates that one entity is capable of using or accommodating different lenses that can be removed and replaced interchangeably.
-
E.
usesLensMount
Indicates that one device or component is designed to accept, attach to, or operate with a specific type of lens mount.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc21838081909872eed21bc12a08 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:50 p.m.