Triple
T11012516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kam language |
E260275
|
entity |
| Predicate | spokenByPopulationEstimate |
P1246
|
FINISHED |
| Object | over 1 million speakers |
—
|
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 speakers | Statement: [Kam language, spokenByPopulationEstimate, over 1 million speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByPopulationEstimate Context triple: [Kam language, spokenByPopulationEstimate, over 1 million speakers]
-
A.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
B.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
C.
hasApproximateNativeSpeakers
chosen
Indicates that an entity is associated with an estimated or approximate number of people who speak it as their native language.
-
D.
usedByPopulation
Indicates that something is utilized or consumed by a specific population or group of people.
-
E.
spokenByCommunity
Indicates that a language, dialect, or expression is used or articulated collectively by a particular community.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7978a57a881909b4ceae0ebe21b78 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.