Triple
T2638607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Milwaukee |
E62807
|
entity |
| Predicate | hasLayParticipationBody |
P39405
|
FINISHED |
| Object | diocesan convention delegates |
—
|
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: diocesan convention delegates | Statement: [Diocese of Milwaukee, hasLayParticipationBody, diocesan convention delegates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayParticipationBody Context triple: [Diocese of Milwaukee, hasLayParticipationBody, diocesan convention delegates]
-
A.
hasLayBody
chosen
Indicates that an entity possesses or is associated with a lay (non-clerical or non-professional) governing or decision-making body.
-
B.
hasGlobalParticipation
Indicates that an entity is involved in or contributes to activities, initiatives, or operations that span multiple countries or have worldwide scope.
-
C.
hasLayMembersCount
Indicates the number of lay (non-clergy or non-professional) members associated with an entity.
-
D.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
E.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8e470ac8190bd0d6de6805afcd0 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.