Triple
T20574723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ælfthryth |
E505184
|
entity |
| Predicate | relativePeriod |
P4343
|
FINISHED |
| Object | late Anglo-Saxon England |
—
|
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: late Anglo-Saxon England | Statement: [Ælfthryth, relativePeriod, late Anglo-Saxon England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePeriod Context triple: [Ælfthryth, relativePeriod, late Anglo-Saxon England]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
relativeChronology
Indicates a temporal ordering relationship that specifies how one event or state is positioned in time relative to another (e.g., earlier, later, or overlapping).
-
C.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
D.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
timePeriodQualifier
Indicates how a time-related statement or value is further specified or constrained, such as by defining its scope, phase, or contextual condition within a broader time period.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a909785c8190a02b1195eadb384c |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.