Triple
T9582762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey of Gengenbach |
E231212
|
entity |
| Predicate | monasticOrderType |
P20285
|
FINISHED |
| Object | Benedictine |
—
|
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: Benedictine | Statement: [Abbey of Gengenbach, monasticOrderType, Benedictine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticOrderType Context triple: [Abbey of Gengenbach, monasticOrderType, Benedictine]
-
A.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
B.
dominantMonasticOrders
Indicates that certain monastic orders hold primary influence, prevalence, or control within a given religious or geographic context.
-
C.
religiousOrderAssociation
chosen
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
D.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
E.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cd59008190888eb11f00f61994 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.