Triple
T3409937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabaul |
E71865
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Tok Pisin |
E49351
|
NE 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: Tok Pisin | Statement: [Rabaul, languageSpoken, Tok Pisin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tok Pisin Context triple: [Rabaul, languageSpoken, Tok Pisin]
-
A.
Tok Pisin
chosen
Tok Pisin is an English-based creole language widely spoken in Papua New Guinea, where it serves as a major lingua franca and one of the country’s primary official languages.
-
B.
Solomon Islands Pijin
Solomon Islands Pijin is an English-based creole language widely used as a lingua franca across the Solomon Islands.
-
C.
Nauruan
Nauruan is an Austronesian language spoken primarily on the Pacific island nation of Nauru.
-
D.
Melanesian Pidgin
Melanesian Pidgin is an English-based creole language widely used as a lingua franca in parts of Melanesia, particularly Papua New Guinea.
-
E.
Tokelauan
Tokelauan refers to the Polynesian people indigenous to Tokelau and their associated language and culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb90754788190ab85e2bec020f99e |
completed | March 8, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b34bdd99248190823875cae2531609 |
completed | March 12, 2026, 11:27 p.m. |
Created at: March 8, 2026, 3:15 p.m.