Triple
T10436421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Riyadi Club Beirut |
E246051
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Al Riyadi |
E246051
|
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: Al Riyadi | Statement: [Al Riyadi Club Beirut, shortName, Al Riyadi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Al Riyadi Context triple: [Al Riyadi Club Beirut, shortName, Al Riyadi]
-
A.
Al Riyadi Club Beirut
chosen
Al Riyadi Club Beirut is a prominent Lebanese professional basketball club based in Beirut, known as one of the most successful and decorated teams in Middle Eastern basketball.
-
B.
Al-Ahli
Al-Ahli is a Qatari professional football club based in Doha and one of the country’s oldest and most historic teams.
-
C.
Al-Nasr
Al-Nasr is a Libyan football club based in Benghazi that competes in the Libyan Premier League.
-
D.
Al-Wehdat SC
Al-Wehdat SC is a prominent Jordanian football club based in Amman, known for its large fan base and success in domestic competitions.
-
E.
Al-Faisaly SC
Al-Faisaly SC is one of Jordan’s most successful and popular football clubs, based in Amman and known for its numerous domestic titles and regional achievements.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea843f1c8190afca4a42bc364468 |
completed | April 7, 2026, 11:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d89f98a2a0819093e029d940c59508 |
completed | April 10, 2026, 6:58 a.m. |
Created at: April 6, 2026, 12:14 p.m.