Triple
T19063643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCIE |
E466598
|
entity |
| Predicate | hasNonRegionalMembers |
P29118
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BCIE, hasNonRegionalMembers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonRegionalMembers Context triple: [BCIE, hasNonRegionalMembers, true]
-
A.
hasNonRegionalMemberCountries
chosen
Indicates that an organization includes member countries that are not part of the primary geographic region with which the organization is associated.
-
B.
hasRegionalOrganizationMembershipViaConstituents
Indicates that an entity is considered a member of a regional organization indirectly, by virtue of its constituent parts or sub-entities holding that membership.
-
C.
hasMemberJurisdictions
Indicates that an administrative or organizational entity includes specific jurisdictions as its constituent members.
-
D.
numberOfRegionalMembers
Indicates the quantity of members associated with or belonging to a specific region within a given context.
-
E.
hasRegionalAffiliation
Indicates that an entity is associated with, belongs to, or is officially linked to a specific geographic region.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e196deac8190ad0406c616197e0b |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.