Triple
T15428010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Íslendingasögur |
E369562
|
entity |
| Predicate | typicalCompositionDate |
P6964
|
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: [Íslendingasögur, typicalCompositionDate, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCompositionDate Context triple: [Íslendingasögur, typicalCompositionDate, 13th century]
-
A.
dateOfComposition
chosen
Indicates the calendar date or time period when a particular work was created or composed.
-
B.
hasUnknownExactDateOfComposition
Indicates that the precise date when a work was composed is not known.
-
C.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
D.
traditionallyDated
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
E.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.