Triple
T30382399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EF-S lens mount |
E772865
|
entity |
| Predicate | compatibleSensorFormat |
P169095
|
FINISHED |
| Object | APS-C |
—
|
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: APS-C | Statement: [Canon EF-S lens mount, compatibleSensorFormat, APS-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleSensorFormat Context triple: [Canon EF-S lens mount, compatibleSensorFormat, APS-C]
-
A.
usedOnSensorFormats
chosen
Indicates that something (such as a method, algorithm, or configuration) is applied to or compatible with specific sensor data formats.
-
B.
sensorFormatSupport
Indicates that a system or device supports a particular data format for a given sensor.
-
C.
formatCompatibleWith
Indicates that one format can be correctly used, interpreted, or processed in conjunction with another format without conflict or loss of information.
-
D.
sensorFormat
Indicates the data encoding or representation standard used by a sensor to output its measurements.
-
E.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 8:01 p.m.