Triple
T21469459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bnei Sakhnin F.C. |
E529684
|
entity |
| Predicate | hasDerbyTypeMatch |
P113569
|
FINISHED |
| Object | matches against Beitar Jerusalem F.C. |
—
|
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: matches against Beitar Jerusalem F.C. | Statement: [Bnei Sakhnin F.C., hasDerbyTypeMatch, matches against Beitar Jerusalem F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerbyTypeMatch Context triple: [Bnei Sakhnin F.C., hasDerbyTypeMatch, matches against Beitar Jerusalem F.C.]
-
A.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
-
B.
isDerby
chosen
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
C.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
D.
hasDerbyColor
Indicates that one entity (typically a derby or race event) is associated with a specific color used to represent or identify it.
-
E.
playsInDerby
Indicates participation by an entity as a competitor or performer in a derby event.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea12d9048190bf51ca3efc435a64 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:16 p.m.