Triple
T21348933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murung River |
E526420
|
entity |
| Predicate | hasLocalLanguageRegion |
P96310
|
FINISHED |
| Object | Dayak languages area |
—
|
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: Dayak languages area | Statement: [Murung River, hasLocalLanguageRegion, Dayak languages area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalLanguageRegion Context triple: [Murung River, hasLocalLanguageRegion, Dayak languages area]
-
A.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
B.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
-
C.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
D.
hasTraditionalLanguageRegion
chosen
Indicates the geographic region traditionally associated with the use or origin of a particular language.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baab4e081908916a289c607cf3a |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:02 p.m.