Triple
T13162621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algerian Cup |
E312763
|
entity |
| Predicate | participatingClubs |
P6630
|
FINISHED |
| Object | Algerian football clubs |
—
|
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: Algerian football clubs | Statement: [Algerian Cup, participatingClubs, Algerian football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingClubs Context triple: [Algerian Cup, participatingClubs, Algerian football clubs]
-
A.
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.
-
B.
topClubsParticipateIn
Indicates that leading or highest-ranked clubs take part in a specified event, competition, or activity.
-
C.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
D.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
-
E.
involvesClub
chosen
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.