Triple
T33425256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | selecciones juveniles de fútbol de Ecuador |
E855957
|
entity |
| Predicate | idioma habitual |
P72909
|
FINISHED |
| Object | español |
—
|
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: español | Statement: [selecciones juveniles de fútbol de Ecuador, idioma habitual, español]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idioma habitual Context triple: [selecciones juveniles de fútbol de Ecuador, idioma habitual, español]
-
A.
typicalLanguageUse
chosen
Indicates that one entity is the language most commonly or habitually used by another entity in ordinary communication or contexts.
-
B.
vernacularOf
Indicates that one language or dialect is the everyday, locally used form corresponding to another, more general or standard language.
-
C.
isColloquial
Indicates that something is expressed in informal, conversational, or non-standard language usage.
-
D.
linguisticUsage
Indicates how a linguistic form, expression, or construction is used in language, such as its typical context, function, or register.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.