Triple
T24471977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Efate–Shepherds area |
E617123
|
entity |
| Predicate | hasColonialLanguage |
P156231
|
FINISHED |
| Object | Bislama |
—
|
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: Bislama | Statement: [Efate–Shepherds area, hasColonialLanguage, Bislama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColonialLanguage Context triple: [Efate–Shepherds area, hasColonialLanguage, Bislama]
-
A.
languageOfColonialSettlers
Indicates the language historically spoken by colonial settlers in a given place or context.
-
B.
officialLanguageDuringColonialPeriod
Indicates that a language served as the official language of administration or governance in a territory during its colonial period.
-
C.
hasColonialHistory
Indicates that an entity has experienced or participated in a period of colonial rule, control, or administration in relation to another entity.
-
D.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
E.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
- F. None of above. chosen
Provenance (4 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29943e9cc81909f1742c778bf3587 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.