Triple
T13011049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Classique |
E322408
|
entity |
| Predicate | derbyClassification |
P81009
|
FINISHED |
| Object | major European football rivalry |
—
|
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: major European football rivalry | Statement: [Le Classique, derbyClassification, major European football rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyClassification Context triple: [Le Classique, derbyClassification, major European football rivalry]
-
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.
typeOfDerby
chosen
Indicates that one entity is a specific kind or category of derby in relation to another entity.
-
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.
derbyFocus
Indicates that something is the main subject, theme, or point of attention within the context of a derby event or competition.
-
E.
derbyInvolves
Indicates that a particular derby event includes or features the participation of a specified entity or entities.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9e14b88190a2cee8e0c9bf31c8 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:49 p.m.