Triple
T20504795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmesbury Abbey |
E503399
|
entity |
| Predicate | earlierFoundation |
P1478
|
FINISHED |
| Object | Anglo-Saxon monastery |
—
|
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: Anglo-Saxon monastery | Statement: [Malmesbury Abbey, earlierFoundation, Anglo-Saxon monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierFoundation Context triple: [Malmesbury Abbey, earlierFoundation, Anglo-Saxon monastery]
-
A.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
B.
foundedBefore
chosen
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
foundationFoundedIn
Indicates that a foundation was established or came into existence in a specific year or time period.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
- 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.