Triple
T1304921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolivian Spanish |
E27852
|
entity |
| Predicate | hasPronounSystem |
P26817
|
FINISHED |
| Object | use of voseo in some eastern regions |
—
|
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: use of voseo in some eastern regions | Statement: [Bolivian Spanish, hasPronounSystem, use of voseo in some eastern regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPronounSystem Context triple: [Bolivian Spanish, hasPronounSystem, use of voseo in some eastern regions]
-
A.
hasNounClassSystem
Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
-
B.
hasPronounForIt
Indicates that one entity serves as the pronoun form referring to another entity.
-
C.
hasPronounForI
Indicates that an entity is associated with or uses a specific pronoun corresponding to the first-person singular "I" in a given language or context.
-
D.
hasPronounForHe
Indicates that an entity is referred to or can be referred to using the pronoun "he."
-
E.
hasPronounForThey
Indicates that one entity serves as the pronoun form corresponding to “they” for another entity.
- F. None of above. chosen
Provenance (4 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13393388190b784d6bd8c447dda |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.