Triple
T31498044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIONZ XR |
E803601
|
entity |
| Predicate | targetUserSegment |
P481
|
FINISHED |
| Object | professional photographers |
—
|
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: professional photographers | Statement: [BIONZ XR, targetUserSegment, professional photographers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUserSegment Context triple: [BIONZ XR, targetUserSegment, professional photographers]
-
A.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
B.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
C.
targetQualification
Indicates that one entity specifies or defines the required qualification or eligibility criteria for another entity.
-
D.
targetUserAction
Indicates that a specific user is the intended recipient or focus of a particular action performed within the system.
-
E.
targetRole
Indicates the specific role or function that an entity is intended or designated to fulfill in a given context.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 30, 2026, 9:42 p.m.