Triple
T33689443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نادي هبوعيل بئر السبع |
E863135
|
entity |
| Predicate | المنافسة |
P17867
|
FINISHED |
| Object | الدوري الإسرائيلي الممتاز |
—
|
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: الدوري الإسرائيلي الممتاز | Statement: [نادي هبوعيل بئر السبع, المنافسة, الدوري الإسرائيلي الممتاز]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: المنافسة Context triple: [نادي هبوعيل بئر السبع, المنافسة, الدوري الإسرائيلي الممتاز]
-
A.
competencia
Indicates that one entity is in a state of competition or rivalry with another, typically striving to achieve a similar goal or advantage.
-
B.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
C.
competitionOf
chosen
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
- 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_69f6fa67cd908190a1784bd212fe3749 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.