Triple
T2947355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuktun |
E79533
|
entity |
| Predicate | hasSpeakerCommunitySize |
P36744
|
FINISHED |
| Object | small population |
—
|
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: small population | Statement: [Inuktun, hasSpeakerCommunitySize, small population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakerCommunitySize Context triple: [Inuktun, hasSpeakerCommunitySize, small population]
-
A.
haveSpeakerPopulation
chosen
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
B.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
C.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
D.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
E.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b5916c8190b1163bf0b7fa136a |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.