Triple
T8438694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Sadd SC |
E199293
|
entity |
| Predicate | rival |
P437
|
FINISHED |
| Object | Al Rayyan SC |
E387457
|
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 Rayyan SC | Statement: [Al Sadd SC, rival, Al Rayyan SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Al Rayyan SC Context triple: [Al Sadd SC, rival, Al Rayyan SC]
-
A.
Al Rayyan SC
chosen
Al Rayyan SC is a prominent Qatari professional football club based in Al Rayyan, known for its large fan base and historic success in domestic competitions.
-
B.
Al Wakrah SC
Al Wakrah SC is a professional football club from Al Wakrah, Qatar, known for competing in the country’s top-tier league and having a long-standing presence in Qatari football.
-
C.
Al Khor SC
Al Khor SC is a professional football club from Al Khor, Qatar, that competes in the country’s top-tier league system.
-
D.
Al Shamal SC
Al Shamal SC is a professional football club from Qatar that competes in the country’s top-tier league.
-
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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe135657c81908ed8156fbfbef6ec |
completed | March 31, 2026, 2:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4dc163488190a53d8696fdba94b5 |
completed | April 2, 2026, 11:06 a.m. |
Created at: March 30, 2026, 6:08 p.m.