Triple
T23449831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Super Cup |
E567746
|
entity |
| Predicate | currentOrganizationalStatus |
P81387
|
FINISHED |
| Object | active competition |
—
|
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: active competition | Statement: [African Super Cup, currentOrganizationalStatus, active competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOrganizationalStatus Context triple: [African Super Cup, currentOrganizationalStatus, active competition]
-
A.
organizationalStatus
chosen
Indicates the current state or condition of an organization within a defined context, such as its operational, legal, or membership status.
-
B.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
C.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
D.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
E.
careerStatus
Indicates the current stage, position, or condition of an entity within its professional or occupational life.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64c1ee081908ba3adf5ce80d6a5 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.