Triple
T28918557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Clasico |
E733440
|
entity |
| Predicate | featuresPopularClubWithLargeFanBase |
P50991
|
FINISHED |
| Object | Al Rayyan SC |
—
|
NE NERFINISHED |
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: [Qatar Clasico, featuresPopularClubWithLargeFanBase, Al Rayyan SC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPopularClubWithLargeFanBase Context triple: [Qatar Clasico, featuresPopularClubWithLargeFanBase, Al Rayyan SC]
-
A.
otherProminentClub
Indicates a relationship where an entity is associated with another club that is also notable or high-profile, distinct from its primary or main club.
-
B.
isOneOfMostPopularClubsIn
Indicates that a club ranks among the most popular clubs within a specified place or context.
-
C.
featuresClubSuccess
Indicates that something highlights or showcases the success or achievements of a club.
-
D.
featuresClubs
chosen
Indicates that something includes or presents one or more clubs as part of its composition, content, or offering.
-
E.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 28, 2026, 8:17 a.m.