Triple
T2630819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Infrastructure |
E59626
|
entity |
| Predicate | roleInNokia |
P8439
|
FINISHED |
| Object | core networks 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 networks business | Statement: [Network Infrastructure, roleInNokia, core networks business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNokia Context triple: [Network Infrastructure, roleInNokia, core networks business]
-
A.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInIndustry
chosen
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
D.
technologyRole
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
E.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.