Triple
T6786744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngero–Vitiaz languages |
E155825
|
entity |
| Predicate | arePrimarilyOral |
P67236
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ngero–Vitiaz languages, arePrimarilyOral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arePrimarilyOral Context triple: [Ngero–Vitiaz languages, arePrimarilyOral, true]
-
A.
hasOralDiscFunction
Indicates that an entity possesses a specific functional role or capability associated with its oral disc.
-
B.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
C.
isSpokenAround
chosen
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
D.
spokenVsWritten
Indicates that the relationship contrasts or distinguishes between spoken and written forms of the same content or expression.
-
E.
performsPrimarilyIn
Indicates that an entity (such as a performer or group) mainly carries out its performances within a particular location, medium, or context.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28f043081909a9a9ab635785933 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.