Triple
T20505047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battle of Maldon |
E503405
|
entity |
| Predicate | survivalState |
P53287
|
FINISHED |
| Object | fragmentary |
—
|
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: fragmentary | Statement: [The Battle of Maldon, survivalState, fragmentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalState Context triple: [The Battle of Maldon, survivalState, fragmentary]
-
A.
hasSurvivalStatus
chosen
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
E.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
- 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_69e69dc539908190a18918fd9b7a829d |
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.