Triple
T6432514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cistercians |
E129810
|
entity |
| Predicate | hasLayAssociation |
P38635
|
FINISHED |
| Object | lay brothers |
—
|
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: lay brothers | Statement: [Cistercians, hasLayAssociation, lay brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayAssociation Context triple: [Cistercians, hasLayAssociation, lay brothers]
-
A.
hasLayOrganizationType
Indicates that an entity is associated with a specific type or category of lay (non-clerical) organizational structure.
-
B.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
-
C.
hasLayBody
Indicates that an entity possesses or is associated with a lay (non-clerical or non-professional) governing or decision-making body.
-
D.
hasLayMembersCount
Indicates the number of lay (non-clergy or non-professional) members associated with an entity.
-
E.
hasLayCommunity
chosen
Indicates that an entity is associated with or includes a lay (non-clerical, non-professional) community as part of its structure or activities.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693de6ac81909f3e330363a52102 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.