Triple
T20880534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Javanese |
E514132
|
entity |
| Predicate | hasPolitenessLevels |
P71062
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Central Javanese, hasPolitenessLevels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolitenessLevels Context triple: [Central Javanese, hasPolitenessLevels, yes]
-
A.
hasPolitenessSystem
Indicates that a language or communication system includes formalized ways of expressing different levels of politeness or social hierarchy.
-
B.
politenessLevel
Indicates the degree of courteousness or respectfulness expressed by one entity toward another in an interaction.
-
C.
hasPolitePronoun
Indicates that one entity refers to another using a polite or honorific form of address in language.
-
D.
honorSystemLevel
Indicates the degree or tier of trust-based behavior or compliance expected or demonstrated within an honor system.
-
E.
hasSpeechLevels
chosen
Indicates that a language, dialect, or communicative system distinguishes different levels or styles of speech used according to social context, formality, or relative status between 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67974348190bd3484032c0d7b31 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.