Triple
T26131130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revesby Abbey |
E659249
|
entity |
| Predicate | religiousOrderOfFormerSite |
P138746
|
FINISHED |
| Object | Cistercian |
—
|
NE NERFINISHED |
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: Cistercian | Statement: [Revesby Abbey, religiousOrderOfFormerSite, Cistercian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderOfFormerSite Context triple: [Revesby Abbey, religiousOrderOfFormerSite, Cistercian]
-
A.
religiousOrderBranchOf
Indicates that one religious order or congregation is an official subdivision, branch, or offshoot of another religious order.
-
B.
religiousOrderName
chosen
Indicates the specific name of the religious order with which an entity is affiliated or associated.
-
C.
religiousOrderAssociation
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
D.
religiousOrderCode
Indicates the specific religious order or denomination with which an entity is affiliated, represented by a standardized code.
-
E.
religiousOrderOrRole
Indicates that an entity has a specific religious affiliation, order, or role within a religious tradition.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 26, 2026, 8:15 p.m.