Triple
T30787424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Aslian languages |
E783991
|
entity |
| Predicate | haveSmallSpeakerPopulations |
P98216
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Northern Aslian languages, haveSmallSpeakerPopulations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSmallSpeakerPopulations Context triple: [Northern Aslian languages, haveSmallSpeakerPopulations, true]
-
A.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
B.
includesLanguagesWithSmallSpeakerPopulations
chosen
Indicates that something contains or covers languages spoken by relatively few people.
-
C.
hasVerySmallResidentPopulation
Indicates that the subject location has a resident population that is extremely small in size.
-
D.
hasSmallBodyPopulation
Indicates that an entity has a relatively low number of small celestial bodies (such as asteroids, comets, or minor planets) associated with it.
-
E.
haveLimitedNumberOfSpeakers
Indicates that the language or communication system is used fluently by only a relatively small number of speakers.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6900ab06c8190856785240a8faa83 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.