Triple
T8355805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murrisk Abbey |
E196677
|
entity |
| Predicate | functionInPast |
P82263
|
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: [Murrisk Abbey, functionInPast, religious community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInPast Context triple: [Murrisk Abbey, functionInPast, religious community]
-
A.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
B.
operatedInThePastTense
Indicates that the action of operating was performed by the subject in the past.
-
C.
hasPastTenseEnding
Indicates that a verb form ends with a morphological marker typically used to express past tense.
-
D.
functionSince
Indicates that one entity has served or operated in a particular role, capacity, or function continuously from a specified starting time or event.
-
E.
positionOnPast
Indicates that one entity occupied a specific position or location relative to another entity at some point in the past.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804a344c819089c0a13fe66e3088 |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.