Triple
T27814243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pershore Abbey |
E702615
|
entity |
| Predicate | lostPart |
P163725
|
FINISHED |
| Object | many conventual buildings |
—
|
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: many conventual buildings | Statement: [Pershore Abbey, lostPart, many conventual buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostPart Context triple: [Pershore Abbey, lostPart, many conventual buildings]
-
A.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
B.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
C.
lostOrDestroyed
Indicates that something has ceased to exist in its original, usable form, either by being misplaced beyond recovery or physically destroyed.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
- F. None of above. chosen
Provenance (4 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 5:44 p.m.