Triple
T33689459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نادي هبوعيل بئر السبع |
E863135
|
entity |
| Predicate | المنافسة المحلية |
P86410
|
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.
localCompetition
chosen
Indicates that two entities are competing with each other within the same local or geographically limited market or area.
-
B.
intraCityDerby
Indicates a competitive match or rivalry that takes place between teams from the same city.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
cityRivalry
Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
-
E.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
- 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.