Triple
T21666962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punan languages |
E534746
|
entity |
| Predicate | ethnologueScope |
P145374
|
FINISHED |
| Object | multiple distinct languages |
—
|
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: multiple distinct languages | Statement: [Punan languages, ethnologueScope, multiple distinct languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnologueScope Context triple: [Punan languages, ethnologueScope, multiple distinct languages]
-
A.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
B.
hasEthnologueEntry
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
C.
ethnolinguisticGroupSize
Indicates the number of individuals belonging to a particular ethnolinguistic group.
-
D.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
E.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
- F. None of above. chosen
Provenance (4 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0c236881909ffaefea8601b1c2 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:37 p.m.