Triple
T6458190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Evangelical Alliance |
E142046
|
entity |
| Predicate | hasRegionalAllianceCount |
P51092
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [World Evangelical Alliance, hasRegionalAllianceCount, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalAllianceCount Context triple: [World Evangelical Alliance, hasRegionalAllianceCount, 7]
-
A.
hasRegionalAffiliation
Indicates that an entity is associated with, belongs to, or is officially linked to a specific geographic region.
-
B.
associatedConfederationCount
Indicates the number of distinct confederations with which an entity is associated.
-
C.
hasAllianceInState
Indicates that an alliance or cooperative relationship exists between entities within a specified state or jurisdiction.
-
D.
hasNonRegionalMemberCountries
Indicates that an organization includes member countries that are not part of the primary geographic region with which the organization is associated.
-
E.
numberOfRegionalMembers
chosen
Indicates the quantity of members associated with or belonging to a specific region within a given context.
- 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_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. |
Created at: March 22, 2026, 4:48 p.m.