Triple
T30774102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-H2 |
E783609
|
entity |
| Predicate | companionModel |
P22642
|
FINISHED |
| Object | Fujifilm X-H2S |
—
|
NE NERFINISHED |
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: Fujifilm X-H2S | Statement: [Fujifilm X-H2, companionModel, Fujifilm X-H2S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionModel Context triple: [Fujifilm X-H2, companionModel, Fujifilm X-H2S]
-
A.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
B.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
C.
companionChip
Indicates that one entity serves as a companion or auxiliary chip to another, typically functioning alongside it to provide additional or supporting capabilities.
-
D.
modeledWith
Indicates that something is represented, simulated, or described using a particular model, method, or modeling technique.
-
E.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 8:40 p.m.