Triple
T35167211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Classico français |
E1015435
|
entity |
| Predicate | hasMatchCategory |
P38353
|
FINISHED |
| Object | derby-like 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: derby-like rivalry | Statement: [Le Classico français, hasMatchCategory, derby-like rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchCategory Context triple: [Le Classico français, hasMatchCategory, derby-like rivalry]
-
A.
matchCategory
chosen
Indicates that two or more entities belong to the same category or share an equivalent classification.
-
B.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
-
C.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.