Triple
T15785838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey of Fécamp |
E382735
|
entity |
| Predicate | reestablishedAsBenedictineAbbey |
P11203
|
FINISHED |
| Object | 1001 |
—
|
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: 1001 | Statement: [Abbey of Fécamp, reestablishedAsBenedictineAbbey, 1001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedAsBenedictineAbbey Context triple: [Abbey of Fécamp, reestablishedAsBenedictineAbbey, 1001]
-
A.
refoundedAsBenedictineMonastery
chosen
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
B.
formerCistercianAbbey
Indicates that something was once a Cistercian abbey but no longer holds that status.
-
C.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
D.
abbeyDenomination
Indicates the religious denomination or order with which an abbey is affiliated.
-
E.
restoredAsArchdiocese
Indicates that an ecclesiastical jurisdiction, previously reduced or altered in status, has been returned to the rank and authority of an archdiocese.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0540380448190a025338f0e62e6d1 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.