Triple
T22587734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehonians |
E564845
|
entity |
| Predicate | hasNonClericalMembers |
P148837
|
FINISHED |
| Object | 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: brothers | Statement: [Dehonians, hasNonClericalMembers, brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonClericalMembers Context triple: [Dehonians, hasNonClericalMembers, brothers]
-
A.
hasClericalMember
Indicates that an entity includes or is associated with a member who performs clerical or administrative duties.
-
B.
hasNonvotingMember
Indicates that an entity is associated with a member who participates in some capacity but does not possess formal voting rights in the relevant decision-making process.
-
C.
hasCommitteeMembers
Indicates that a committee is composed of, or includes, specific individuals as its members.
-
D.
hasNonBorrowingMembers
Indicates that an entity has members who are not involved in borrowing (e.g., do not take loans or credit) within the specified context.
-
E.
hasIndependentMembers
Indicates that an entity includes members who act or operate autonomously, without being controlled or directed by the entity or by each other.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615de7d48190b1ca46c76a1e609c |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:46 p.m.