Triple
T21288853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widsith |
E524733
|
entity |
| Predicate | probableCompositionPeriod |
P84263
|
FINISHED |
| Object | early Anglo-Saxon period |
—
|
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: early Anglo-Saxon period | Statement: [Widsith, probableCompositionPeriod, early Anglo-Saxon period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: probableCompositionPeriod Context triple: [Widsith, probableCompositionPeriod, early Anglo-Saxon period]
-
A.
probableCenturyOfComposition
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
B.
approximateInceptionPeriod
chosen
Indicates an estimated or loosely defined time period during which something began or came into existence.
-
C.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
D.
deciphermentPeriod
Indicates the time span during which the decipherment of something (such as a script, code, or text) took place.
-
E.
dateOfCompositionHypothesis
Indicates a hypothesized or uncertain date when something (such as a work or document) was composed.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d882408190a2300327cb73b7f6 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.