Triple
T217596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aymara |
E4140
|
entity |
| Predicate | approximateSpeakers |
P1247
|
FINISHED |
| Object | over 1 million |
—
|
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: over 1 million | Statement: [Aymara, approximateSpeakers, over 1 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSpeakers Context triple: [Aymara, approximateSpeakers, over 1 million]
-
A.
hasApproximateTotalSpeakers
chosen
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
B.
hasApproximateNativeSpeakers
Indicates that an entity is associated with an estimated or approximate number of people who speak it as their native language.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
hasNativeSpeakers
Indicates that a language or dialect is spoken as a first language by one or more people or populations.
-
E.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5062e48190833be10e4770e1e9 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.