Triple
T36186546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnamagnæan Manuscript Collection |
E1046861
|
entity |
| Predicate | secondaryRepository |
P100462
|
FINISHED |
| Object | Reykjavík |
—
|
NE NERFINISHED |
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: Reykjavík | Statement: [Arnamagnæan Manuscript Collection, secondaryRepository, Reykjavík]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryRepository Context triple: [Arnamagnæan Manuscript Collection, secondaryRepository, Reykjavík]
-
A.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryBranch
Indicates that one entity functions as a secondary or subordinate branch in relation to another primary or main branch entity.
-
D.
secondarySite
chosen
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
-
E.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:08 p.m.