Triple
T3962462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Saxons |
E85935
|
entity |
| Predicate | historicalDisappearance |
P17309
|
FINISHED |
| Object | assimilated into broader English identity |
—
|
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: assimilated into broader English identity | Statement: [Middle Saxons, historicalDisappearance, assimilated into broader English identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDisappearance Context triple: [Middle Saxons, historicalDisappearance, assimilated into broader English identity]
-
A.
yearOfDisappearance
Indicates the specific year in which an entity disappeared or ceased to be present.
-
B.
placeOfDisappearance
Indicates the location where an entity was last seen or went missing.
-
C.
disappearance
chosen
Indicates that an entity ceases to be present, visible, or detectable in a given context or location.
-
D.
disappearedDuring
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
-
E.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.