Triple
T8697909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rushen Abbey |
E206446
|
entity |
| Predicate | primaryFunctionMedieval |
P84615
|
FINISHED |
| Object | religious community |
—
|
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: religious community | Statement: [Rushen Abbey, primaryFunctionMedieval, religious community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionMedieval Context triple: [Rushen Abbey, primaryFunctionMedieval, religious community]
-
A.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
B.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
C.
isMedieval
Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
-
D.
medievalLordship
Indicates a feudal relationship in which one entity holds authority, control, or dominion over another in a medieval lord–vassal or territorial context.
-
E.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58af50408190a3b81100a759795e |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:34 p.m.