Triple
T34196072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guayaquil football derbies |
E877244
|
entity |
| Predicate | mainDerby |
P113569
|
FINISHED |
| Object | Clásico del Astillero |
—
|
NE NERFINISHED |
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: Clásico del Astillero | Statement: [Guayaquil football derbies, mainDerby, Clásico del Astillero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDerby Context triple: [Guayaquil football derbies, mainDerby, Clásico del Astillero]
-
A.
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.
-
B.
regionDerby
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
C.
relatedDerby
Indicates that two entities are connected through participation in, association with, or relevance to the same derby event or competition.
-
D.
isDerbyIn
Indicates that a derby (typically a sports match or rivalry game) takes place within or belongs to a particular location or competition context.
-
E.
homeDerbyName
Indicates the name of the derby event or match that is played at the entity’s home venue.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:55 a.m.