Triple
T452503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia Devices and Services business |
E7157
|
entity |
| Predicate | servedRoleWithinNokia |
P11687
|
FINISHED |
| Object | core handset division |
—
|
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 handset division | Statement: [Nokia Devices and Services business, servedRoleWithinNokia, core handset division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedRoleWithinNokia Context triple: [Nokia Devices and Services business, servedRoleWithinNokia, core handset division]
-
A.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
B.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
C.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
D.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
E.
roleWithinRaytheon
Indicates that one entity holds or has held a specific role, position, or function within the organization Raytheon.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef854f7481909dc2207faf0327ec |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.