Triple
T7073844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern African Customs Union |
E164764
|
entity |
| Predicate | usesRevenueSharingFormula |
P9389
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Southern African Customs Union, usesRevenueSharingFormula, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRevenueSharingFormula Context triple: [Southern African Customs Union, usesRevenueSharingFormula, yes]
-
A.
revenueUse
chosen
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
B.
allianceCurrencySharing
Indicates that members of an alliance share or coordinate the use, management, or benefits of a common currency or monetary system.
-
C.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
D.
supportsShares
Indicates that one entity provides assistance, endorsement, or resources to another entity in the context of shared ownership, shared resources, or jointly held interests.
-
E.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ccb42c81909f5627aa97db7a84 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.