Triple
T24435190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kisar people |
E616105
|
entity |
| Predicate | ethnoLinguisticFamily |
P46225
|
FINISHED |
| Object | Austronesian peoples |
—
|
NE NERFINISHED |
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: Austronesian peoples | Statement: [Kisar people, ethnoLinguisticFamily, Austronesian peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoLinguisticFamily Context triple: [Kisar people, ethnoLinguisticFamily, Austronesian peoples]
-
A.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
B.
ethnolinguisticGroups
chosen
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
C.
majorLanguageFamilies
Indicates that one entity is a primary or dominant language family to which the other entity (a language or group of languages) belongs.
-
D.
ethnonymLanguageFamily
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
E.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978638888190aef3ab5fc8bf0ed4 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.