Triple
T16771668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wehdat |
E407611
|
entity |
| Predicate | rival |
P437
|
FINISHED |
| Object | Al-Faisaly SC |
E87950
|
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-Faisaly SC | Statement: [Wehdat, rival, Al-Faisaly SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Al-Faisaly SC Context triple: [Wehdat, rival, Al-Faisaly SC]
-
A.
Al-Faisaly SC
chosen
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.
-
B.
Al-Faisaly FC
Al-Faisaly FC is a Saudi Arabian professional football club known for competing in the Saudi league system and for its regional rivalries, including a notable one with Al Fayha FC.
-
C.
Al-Hussein SC
Al-Hussein SC is a professional football club based in Irbid, Jordan, competing in the Jordanian Pro League.
-
D.
Al-Salt SC
Al-Salt SC is a professional football club from Al-Salt, Jordan, that competes in the country’s top-tier Jordanian Pro League.
-
E.
Al Shamal SC
Al Shamal SC is a professional football club from Qatar that competes in the country’s top-tier league.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b036ff788190bd9f166c3f127818 |
completed | April 18, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180bf3d308190b4965d57fe327a52 |
completed | May 11, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:21 a.m.