Triple
T30735504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochabamba derby |
E782541
|
entity |
| Predicate | languageUsedByFans |
P3778
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Cochabamba derby, languageUsedByFans, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedByFans Context triple: [Cochabamba derby, languageUsedByFans, Spanish]
-
A.
languageOfFanbase
chosen
Indicates the primary language or languages commonly used by a fanbase in its communication and expression.
-
B.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
C.
languageDiscussedIn
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
-
D.
languageUsedByOpponents
Indicates that a particular language is used by entities who are opponents in some context (e.g., conflict, competition, or rivalry).
-
E.
languageOfSocialSphere
Indicates the language predominantly used within a particular social group, community, or social context.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 29, 2026, 8:37 p.m.