Triple
T34809981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsey Abbey |
E1003470
|
entity |
| Predicate | statusInMiddleAges |
P46137
|
FINISHED |
| Object | one of the wealthiest monasteries in 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: one of the wealthiest monasteries in England | Statement: [Ramsey Abbey, statusInMiddleAges, one of the wealthiest monasteries in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInMiddleAges Context triple: [Ramsey Abbey, statusInMiddleAges, one of the wealthiest monasteries in England]
-
A.
statusIn15thCentury
Indicates the status, condition, or standing that an entity had specifically during the 15th century.
-
B.
statusInThirdAge
Indicates the role, condition, or standing an entity has during the Third Age period.
-
C.
medievalStatus
chosen
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
D.
officeStatusByLateMiddleAges
Indicates the status or condition of an office or position as it existed or was defined by the Late Middle Ages.
-
E.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 3:59 p.m.