Triple
T37447593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graflex camera |
E930588
|
entity |
| Predicate | typicalLensMount |
P33676
|
FINISHED |
| Object | Graflex lens board |
E930588
|
NE 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: Graflex lens board | Statement: [Graflex camera, typicalLensMount, Graflex lens board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLensMount Context triple: [Graflex camera, typicalLensMount, Graflex lens board]
-
A.
usesLensMount
chosen
Indicates that one device or component is designed to accept, attach to, or operate with a specific type of lens mount.
-
B.
lensType
Indicates the specific kind or category of lens associated with or used by an entity.
-
C.
cameraLensType
Indicates the specific type or category of lens used or associated with a camera.
-
D.
supportsInterchangeableLenses
Indicates that one entity is capable of using or accommodating different lenses that can be removed and replaced interchangeably.
-
E.
laterLensType
Indicates that one lens type occurs or is used at a later time than another lens type in a temporal sequence.
- F. None of above.
Provenance (4 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40825f77ac8190b6e38fc8216a406e |
completed | June 28, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.