Triple
T25377254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEC Treaty |
E633087
|
entity |
| Predicate | memberParties |
P98307
|
FINISHED |
| Object | African Union member states |
—
|
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: African Union member states | Statement: [AEC Treaty, memberParties, African Union member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberParties Context triple: [AEC Treaty, memberParties, African Union member states]
-
A.
addressesParties
Indicates that one entity formally directs communication, documentation, or statements to specific parties as their intended recipients.
-
B.
componentParty
chosen
Indicates that one party functions as a constituent or member of a larger party or group within a composite relationship.
-
C.
collaboratingParty
Indicates that an entity is actively working together with another entity toward a shared goal, project, or activity.
-
D.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
E.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:38 p.m.