Triple
T30358464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Imaging business |
E772207
|
entity |
| Predicate | roleInSony |
P199744
|
FINISHED |
| Object | core technology business |
—
|
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: core technology business | Statement: [Sony Imaging business, roleInSony, core technology business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSony Context triple: [Sony Imaging business, roleInSony, core technology business]
-
A.
roleAtNintendo
Indicates that an entity holds or held a specific role or position within the Nintendo organization.
-
B.
roleInToyota
Indicates that one entity holds a specific role, position, or function within the organization Toyota.
-
C.
roleInToyotaGroup
Indicates that an entity holds a specific role or position within the organizational structure of the Toyota Group.
-
D.
roleAtActivision
Indicates that an entity holds or held a specific role or position at Activision.
-
E.
roleInNintendo3DS
Indicates that an entity has a specific role or involvement in relation to the Nintendo 3DS platform or product.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69ff5337e6f88190ae0418335477063c |
completed | May 9, 2026, 3:31 p.m. |
Created at: April 29, 2026, 7:57 p.m.