Triple
T29656410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furness Abbey |
E750278
|
entity |
| Predicate | joinedCistercianOrder |
P99929
|
FINISHED |
| Object | 1147 |
—
|
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: 1147 | Statement: [Furness Abbey, joinedCistercianOrder, 1147]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedCistercianOrder Context triple: [Furness Abbey, joinedCistercianOrder, 1147]
-
A.
enteredSocietyOfJesusAt
Indicates that a person joined or was admitted into the Society of Jesus (the Jesuit order) at a specific time or place.
-
B.
religiousOrderBranchOf
Indicates that one religious order or congregation is an official subdivision, branch, or offshoot of another religious order.
-
C.
convertedToCarthusianMonasteryIn
Indicates that something was transformed into a Carthusian monastery in a specific place or at a specific time.
-
D.
monasteryOrder
chosen
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
E.
religiousOrderSucceededBy
Indicates that one religious order is replaced or followed by another as its successor in a historical or organizational sequence.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f2850288190a394272ae49084e3 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:55 p.m.