Triple
T21148993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VV |
E521133
|
entity |
| Predicate | projectionCompatibility |
P143065
|
FINISHED |
| Object | standard 35 mm projectors via reduction prints |
—
|
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: standard 35 mm projectors via reduction prints | Statement: [VV, projectionCompatibility, standard 35 mm projectors via reduction prints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectionCompatibility Context triple: [VV, projectionCompatibility, standard 35 mm projectors via reduction prints]
-
A.
regionCompatibility
Indicates that two entities are suitable or allowed to coexist, operate, or interact within the same geographic or jurisdictional region.
-
B.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
C.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
D.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
E.
layoutCompatibility
Indicates that two layouts can coexist or be used interchangeably without causing conflicts or usability issues.
- F. None of above. chosen
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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723ffb578819080a000987459a8a5 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.