Triple
T1277369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Solomonic languages |
E27244
|
entity |
| Predicate | hasSoundChange |
P9128
|
FINISHED |
| Object | innovations from Proto-Oceanic |
—
|
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: innovations from Proto-Oceanic | Statement: [Northwest Solomonic languages, hasSoundChange, innovations from Proto-Oceanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundChange Context triple: [Northwest Solomonic languages, hasSoundChange, innovations from Proto-Oceanic]
-
A.
hasPhonologicalChange
chosen
Indicates a relationship where one linguistic form undergoes a change in its sound structure relative to another form or earlier state.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
D.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
E.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.