Triple
T20505136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deor |
E503407
|
entity |
| Predicate | approximateCenturyOfComposition |
P41949
|
FINISHED |
| Object | 10th century or earlier |
—
|
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: 10th century or earlier | Statement: [Deor, approximateCenturyOfComposition, 10th century or earlier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCenturyOfComposition Context triple: [Deor, approximateCenturyOfComposition, 10th century or earlier]
-
A.
probableCenturyOfComposition
chosen
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
B.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
C.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
D.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
E.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc66f00819083c804535e045545 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.