Triple
T8217181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Brothers |
E191961
|
entity |
| Predicate | hasLayCollaborators |
P81540
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Christian Brothers, hasLayCollaborators, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayCollaborators Context triple: [Christian Brothers, hasLayCollaborators, yes]
-
A.
hasLayMembersCount
Indicates the number of lay (non-clergy or non-professional) members associated with an entity.
-
B.
collaboratorsInclude
Indicates that a specified collaborator is included among the collaborators associated with an entity or activity.
-
C.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
D.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
E.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776f41108190bed1c6a8ddbea374 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.