Triple
T28649035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DFMS |
E725140
|
entity |
| Predicate | corporateBodyOf |
P165169
|
FINISHED |
| Object | The Episcopal Church |
—
|
NE NERFINISHED |
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: The Episcopal Church | Statement: [DFMS, corporateBodyOf, The Episcopal Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateBodyOf Context triple: [DFMS, corporateBodyOf, The Episcopal Church]
-
A.
governmentBodyOf
Indicates that one entity is the official governing body or authority responsible for administering, managing, or overseeing the other entity.
-
B.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
C.
governmentBodyRepresented
Indicates that one entity serves as the official representative or acting body on behalf of a particular government or governmental authority.
-
D.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
E.
collectiveBody
Indicates that multiple individuals are grouped and act together as a single collective entity or body.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 4:50 a.m.