Triple
T30358368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-mount |
E772205
|
entity |
| Predicate | compatibleWithBrand |
P90215
|
FINISHED |
| Object | Fujifilm |
—
|
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 | Statement: [Fujifilm X-mount, compatibleWithBrand, Fujifilm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWithBrand Context triple: [Fujifilm X-mount, compatibleWithBrand, Fujifilm]
-
A.
compatibleBrand
chosen
Indicates that one brand is suitable for use with, or functions properly alongside, another brand.
-
B.
supportsBrand
Indicates that one entity endorses, promotes, or is compatible with a particular brand.
-
C.
containsComponentBrand
Indicates that an entity includes, as part of its composition or structure, a component produced or branded by a specified brand.
-
D.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
E.
usesSameBrandFamilyAs
Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 7:57 p.m.