Triple
T4101520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Faisaly SC |
E87950
|
entity |
| Predicate | rival |
P437
|
FINISHED |
| Object | Al-Wehdat SC |
E89429
|
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-Wehdat SC | Statement: [Al-Faisaly SC, rival, Al-Wehdat SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Al-Wehdat SC Context triple: [Al-Faisaly SC, rival, Al-Wehdat SC]
-
A.
Al-Wehdat SC
chosen
Al-Wehdat SC is a prominent Jordanian football club based in Amman, known for its large fan base and success in domestic competitions.
-
B.
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.
-
C.
Sulaymaniyah SC
Sulaymaniyah SC is a professional football club based in Sulaymaniyah, Iraq, competing in the Iraqi football 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 Sailiya SC
Al Sailiya SC is a professional football club based in Al Sailiya, Qatar, known for competing in the country’s top-tier league system.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0ed168819093c83ba079d6725c |
completed | March 9, 2026, 5:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b589d825c48190b4208b0502c257bb |
completed | March 14, 2026, 4:16 p.m. |
Created at: March 9, 2026, 3:40 p.m.