Triple

T14445574
Position Surface form Disambiguated ID Type / Status
Subject Lae E358196 entity
Predicate languageUsed P238 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: [Lae, languageUsed, Tok Pisin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tok Pisin
Context triple: [Lae, languageUsed, 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. Papua New Guinean Hiri Motu
    Papua New Guinean Hiri Motu is an Austronesian-based lingua franca and simplified form of Motu historically used for interethnic communication in Papua New Guinea.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de915e76f481909fe9462f964b5b1c completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd648d8904819084d720a0fd2ddb4b completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:19 a.m.