Triple
T33399800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAF member clubs |
E855265
|
entity |
| Predicate | includeClubsFrom |
P183578
|
FINISHED |
| Object | North Africa |
E2576
|
NE 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: North Africa | Statement: [CAF member clubs, includeClubsFrom, North Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeClubsFrom Context triple: [CAF member clubs, includeClubsFrom, North Africa]
-
A.
formerlyIncludedClubsFrom
Indicates that the subject entity previously included, as part of its organization or membership, the clubs originating from the object entity.
-
B.
includesClubFromLeague
Indicates that a collection or group contains at least one club that belongs to a specified league.
-
C.
includesInvitedClubs
Indicates that certain clubs are explicitly included among those invited to participate in a given event or context.
-
D.
participatingClubsFrom
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
-
E.
alsoInvolvesClubsFrom
chosen
Indicates that an event, action, or relationship includes participation or involvement of clubs originating from a specified place or region.
- F. None of above.
Provenance (4 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0316136a14819085bb88563d5abc42 |
completed | May 12, 2026, 11:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576f57ee08190a8789853e3940533 |
completed | June 19, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a03158a962c81909f17d58197f6ba00 |
completed | May 12, 2026, 11:56 a.m. |
Created at: May 1, 2026, 1:35 a.m.