Triple
T21048713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian National Archives |
E518516
|
entity |
| Predicate | archivesDomain |
P53210
|
FINISHED |
| Object | national history of Norway |
—
|
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: national history of Norway | Statement: [Norwegian National Archives, archivesDomain, national history of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesDomain Context triple: [Norwegian National Archives, archivesDomain, national history of Norway]
-
A.
archiveURL
Indicates that there is a URL pointing to an archived or preserved version of the referenced resource.
-
B.
archivesScope
chosen
Indicates that one entity defines or delimits the scope or coverage of another entity’s archival content or records.
-
C.
archivesOnlineService
Indicates that an online service provides access to or manages digital archives or archived materials.
-
D.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
E.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd79830881909fdac2f0ea48d28c |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.