Triple
T6005784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid Derby |
E133706
|
entity |
| Predicate | derbyInvolves |
P68699
|
FINISHED |
| Object | European competitions |
—
|
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: European competitions | Statement: [Madrid Derby, derbyInvolves, European competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyInvolves Context triple: [Madrid Derby, derbyInvolves, European competitions]
-
A.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
B.
regionDerby
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
C.
derbyInLeagueSystem
Indicates that a derby (a match between local rivals) takes place within, and is organized as part of, a specific league system.
-
D.
playsInDerby
Indicates participation by an entity as a competitor or performer in a derby event.
-
E.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
- F. None of above. chosen
Provenance (4 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f128354819088971ee398cbda77 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.