Triple
T180459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quechua |
E3862
|
entity |
| Predicate | languageStatus |
P4185
|
FINISHED |
| Object | official language in Peru |
—
|
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: official language in Peru | Statement: [Quechua, languageStatus, official language in Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageStatus Context triple: [Quechua, languageStatus, official language in Peru]
-
A.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
B.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
E.
isLanguageOf
chosen
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25901a9188190b8f510bec8c8e7f2 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.