Triple
T24966723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Melanesian languages |
E624766
|
entity |
| Predicate | includeLanguagesSpokenIn |
P56225
|
FINISHED |
| Object | Tanna Island |
—
|
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: Tanna Island | Statement: [Southern Melanesian languages, includeLanguagesSpokenIn, Tanna Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeLanguagesSpokenIn Context triple: [Southern Melanesian languages, includeLanguagesSpokenIn, Tanna Island]
-
A.
includesLanguagesSpokenBy
Indicates that one entity contains or covers the set of languages spoken by another entity.
-
B.
includesLanguagesSpokenAlong
chosen
Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 6 a.m.