Triple
T24307553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occupatio |
E612575
|
entity |
| Predicate | monasticContext |
P12141
|
FINISHED |
| Object | Benedictine |
—
|
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: Benedictine | Statement: [Occupatio, monasticContext, Benedictine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticContext Context triple: [Occupatio, monasticContext, Benedictine]
-
A.
monasticModel
Indicates a relationship where one entity serves as a pattern, example, or standard of monastic life or practice for another entity.
-
B.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
C.
monasticTradition
chosen
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
D.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
E.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922821248190a1b274f839251ddc |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:31 a.m.