Triple
T2530672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Florida |
E56149
|
entity |
| Predicate | hasLayBody |
P39405
|
FINISHED |
| Object | lay delegates to Diocesan Convention |
—
|
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 delegates to Diocesan Convention | Statement: [Diocese of Florida, hasLayBody, lay delegates to Diocesan Convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayBody Context triple: [Diocese of Florida, hasLayBody, lay delegates to Diocesan Convention]
-
A.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
-
B.
hasLayMembersCount
Indicates the number of lay (non-clergy or non-professional) members associated with an entity.
-
C.
hasLie
Indicates that an entity is associated with or responsible for a specific lie or false statement.
-
D.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
E.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd276930c8190bd46b52e06b7098e |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd18e72a88190bdcf12b326d42fad |
completed | March 7, 2026, 7:19 a.m. |
Created at: March 6, 2026, 9:46 p.m.