Triple
T579941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish media |
E15033
|
entity |
| Predicate | digitalizationLevel |
P2086
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Finnish media, digitalizationLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalizationLevel Context triple: [Finnish media, digitalizationLevel, high]
-
A.
technologyLevel
chosen
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
B.
urbanizationLevel
Indicates the degree to which an area or population is characterized by urban development, infrastructure, and density of human settlement.
-
C.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
D.
hasDigitalInitiative
Indicates that an entity is engaged in or associated with a specific digital project, program, or transformation effort.
-
E.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b82b5248190ac863407e8207a3b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.