Triple
T15204658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skírnismál |
E363357
|
entity |
| Predicate | manuscriptCentury |
P117112
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Skírnismál, manuscriptCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manuscriptCentury Context triple: [Skírnismál, manuscriptCentury, 13th century]
-
A.
manuscriptTradition
Indicates the relationship between a text and the chain of manuscript copying, transmission, and variation through which that text has been preserved and passed down.
-
B.
manuscriptDiscoveredBy
Indicates that a manuscript was found or brought to light through the efforts or actions of a particular agent or entity.
-
C.
manuscriptMedium
Indicates the material or physical medium on which a manuscript is written or produced.
-
D.
manuscript
Indicates that an entity is a written or typed document, often a draft or original version of a text, associated with another entity (such as its author, subject, or publication process).
-
E.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
- F. None of above. chosen
Provenance (4 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b7964c8190bc8dc3444b94f15e |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:11 a.m.