Triple
T6458214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Evangelical Alliance |
E142046
|
entity |
| Predicate | hasGlobalNetworkType |
P71105
|
FINISHED |
| Object | association of churches |
—
|
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: association of churches | Statement: [World Evangelical Alliance, hasGlobalNetworkType, association of churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalNetworkType Context triple: [World Evangelical Alliance, hasGlobalNetworkType, association of churches]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
C.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
D.
hasNetworkSize
Indicates the total number of nodes, members, or connections that make up a given network.
-
E.
hasGlobalRegion
Indicates that an entity is associated with or belongs to a specific global geographic region.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d758508190b9c7358ef84f8169 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c068cb3b888190812ed56f2fdd45ed |
completed | March 22, 2026, 10:10 p.m. |
Created at: March 22, 2026, 4:48 p.m.