Triple
T2040578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Council of Churches |
E44733
|
entity |
| Predicate | hasMemberChurches |
P12144
|
FINISHED |
| Object | over 350 |
—
|
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: over 350 | Statement: [World Council of Churches, hasMemberChurches, over 350]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberChurches Context triple: [World Council of Churches, hasMemberChurches, over 350]
-
A.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
-
B.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
hasNumberOfChurches
chosen
Indicates the relationship that specifies how many churches are associated with a given entity.
-
D.
isEstablishedChurchIn
Indicates that a church is officially recognized and established as the state or national church within a specified jurisdiction or territory.
-
E.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.