Triple
T33263547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Löyöp language |
E851584
|
entity |
| Predicate | hasLexicalOrigin |
P124938
|
FINISHED |
| Object | Proto-Oceanic |
—
|
NE NERFINISHED |
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: Proto-Oceanic | Statement: [Löyöp language, hasLexicalOrigin, Proto-Oceanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLexicalOrigin Context triple: [Löyöp language, hasLexicalOrigin, Proto-Oceanic]
-
A.
hasLexicalCategoryOfOrigin
Indicates that one entity originates from, or is derived based on, the lexical category (such as noun, verb, adjective, etc.) of another entity.
-
B.
hasEtymologicalBasis
chosen
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
C.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
D.
hasEtymologyConcept
Indicates that something derives its origin, form, or meaning from a particular etymological concept or source.
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:32 a.m.