Triple
T1223981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongan language group |
E26284
|
entity |
| Predicate | hasMorphosyntacticType |
P1250
|
FINISHED |
| Object | moderately analytic |
—
|
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: moderately analytic | Statement: [Tongan language group, hasMorphosyntacticType, moderately analytic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphosyntacticType Context triple: [Tongan language group, hasMorphosyntacticType, moderately analytic]
-
A.
hasMorphologicalType
chosen
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
B.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
grammaticalType
Indicates the grammatical category or role (such as part of speech or syntactic function) that an expression has within a language.
-
E.
hasLinguisticFeature
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be233fd88190996faf4105c0b8d7 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.