Triple
T26955058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioner of the African Union |
E678876
|
entity |
| Predicate | hasPortfolioExamples |
P46877
|
FINISHED |
| Object | Peace and Security |
—
|
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: Peace and Security | Statement: [Commissioner of the African Union, hasPortfolioExamples, Peace and Security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortfolioExamples Context triple: [Commissioner of the African Union, hasPortfolioExamples, Peace and Security]
-
A.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
B.
hasNotableWorkExample
Indicates that an entity has a specific notable work cited as an example associated with it.
-
C.
workCatalogue
Indicates a relationship where a work is included in, documented by, or associated with a specific catalogue.
-
D.
typicalPortfolio
chosen
Indicates that one entity is the standard or representative portfolio associated with another entity (such as a person, account, or organization).
-
E.
hasVenuePortfolio
Indicates that an entity maintains or owns a collection or portfolio of venues.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 6:27 a.m.