Triple
T16254523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmanian languages |
E394594
|
entity |
| Predicate | numberOfVarietiesEstimated |
P49018
|
FINISHED |
| Object | 8 to 12 |
—
|
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: 8 to 12 | Statement: [Tasmanian languages, numberOfVarietiesEstimated, 8 to 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVarietiesEstimated Context triple: [Tasmanian languages, numberOfVarietiesEstimated, 8 to 12]
-
A.
hasApproximateNumberOfVarieties
chosen
Indicates that an entity is associated with an estimated or non-exact count of different varieties or types.
-
B.
numberOfPrimaryVarieties
Indicates the count of distinct primary varieties associated with a given entity.
-
C.
has32Varieties
Indicates that one entity possesses or includes exactly 32 distinct types, forms, or varieties of another entity.
-
D.
hasVarietyOf
Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
-
E.
estimatedPreContactVarieties
Indicates the estimated number or range of distinct varieties (such as languages or dialects) that existed before initial contact with another group or influence.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24599861881908b9235f005d80a96 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.