Triple

T20068993
Position Surface form Disambiguated ID Type / Status
Subject Gillian Sankoff E499683 entity
Predicate studied P778 FINISHED
Object Tok Pisin 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: Tok Pisin | Statement: [Gillian Sankoff, studied, Tok Pisin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tok Pisin
Context triple: [Gillian Sankoff, studied, 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 (2 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e664365ad0819089103b00d1cf8c9f completed April 20, 2026, 5:36 p.m.
Created at: April 11, 2026, 3:39 p.m.