Triple
T33689456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نادي هبوعيل بئر السبع |
E863135
|
entity |
| Predicate | الرياضة الأخرى المحتملة |
P17808
|
FINISHED |
| Object | فرق فئات سنية في كرة القدم |
—
|
LITERAL 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: فرق فئات سنية في كرة القدم | Statement: [نادي هبوعيل بئر السبع, الرياضة الأخرى المحتملة, فرق فئات سنية في كرة القدم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: الرياضة الأخرى المحتملة Context triple: [نادي هبوعيل بئر السبع, الرياضة الأخرى المحتملة, فرق فئات سنية في كرة القدم]
-
A.
secondarySport
chosen
Indicates that an entity participates in or is associated with a sport that is not their primary or main sport.
-
B.
otherSportsCovered
Indicates that additional sports, beyond a primary or main sport, are also included or reported on.
-
C.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
D.
multiSport
Indicates that an entity participates in, is associated with, or is designed for more than one sport.
-
E.
sportCreatedAsAlternativeTo
Indicates that one sport was developed specifically to serve as a substitute or alternative to another sport.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:43 a.m.