Triple
T19209207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aymaran languages |
E480312
|
entity |
| Predicate | numberOfLivingLanguages |
P13692
|
FINISHED |
| Object | approximately 2–3 |
—
|
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: approximately 2–3 | Statement: [Aymaran languages, numberOfLivingLanguages, approximately 2–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLivingLanguages Context triple: [Aymaran languages, numberOfLivingLanguages, approximately 2–3]
-
A.
numberOfMajorLanguages
Indicates the total count of major languages associated with a given entity.
-
B.
estimatedNumberOfLanguages
Indicates the approximate count of distinct languages associated with an entity, typically based on estimation rather than an exact measurement.
-
C.
extantLanguage
Indicates that a language currently exists or is in active use, as opposed to being extinct or only historically attested.
-
D.
hasApproximateNumberOfLanguages
chosen
Indicates that an entity is associated with a quantity representing an estimated or non-exact count of languages.
-
E.
currentNumberOfLanguages
Indicates the present count of distinct languages associated with or used by a given entity.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a000188190afb762ea24bc3deb |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:20 p.m.