Triple
T6229487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Tongan |
E139317
|
entity |
| Predicate | hasPhonologicalStandard |
P69033
|
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: [Standard Tongan, hasPhonologicalStandard, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonologicalStandard Context triple: [Standard Tongan, hasPhonologicalStandard, yes]
-
A.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
B.
nationalLanguageStandardizedIn
Indicates that a national language has been formally standardized or codified within a particular country or jurisdiction.
-
C.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
D.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
E.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d9a33c8190b66dbd89e0e3bbba |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:22 p.m.