Triple
T18829614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denny Abbey |
E460486
|
entity |
| Predicate | functionDuringMonasticPeriod |
P37071
|
FINISHED |
| Object | religious house |
—
|
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 house | Statement: [Denny Abbey, functionDuringMonasticPeriod, religious house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringMonasticPeriod Context triple: [Denny Abbey, functionDuringMonasticPeriod, religious house]
-
A.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
B.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
C.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
D.
monasticCode
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
-
E.
monasticLifeRestored
Indicates that a previously discontinued or diminished monastic way of life has been reestablished or revived.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a9981be88190b709c0e72ad3f7e6 |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.