Triple
T22368056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguayan Clásico |
E552960
|
entity |
| Predicate | relatedDerbyType |
P75837
|
FINISHED |
| Object | city derby |
—
|
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: city derby | Statement: [Uruguayan Clásico, relatedDerbyType, city derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDerbyType Context triple: [Uruguayan Clásico, relatedDerbyType, city derby]
-
A.
relatedDerby
chosen
Indicates that two entities are connected through participation in, association with, or relevance to the same derby event or competition.
-
B.
typeOfDerby
Indicates that one entity is a specific kind or category of derby in relation to another entity.
-
C.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
D.
derbyInvolves
Indicates that a particular derby event includes or features the participation of a specified entity or entities.
-
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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580229688190a6e5e02b484033f7 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.