Triple

T1945880
Position Surface form Disambiguated ID Type / Status
Subject Austroasiatic E42054 entity
Predicate hasLanguage P15 FINISHED
Object Pearic E216898 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: Pearic | Statement: [Austroasiatic, hasLanguage, Pearic]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pearic
Context triple: [Austroasiatic, hasLanguage, Pearic]
  • A. Pearic chosen
    Pearic is a small branch of Austroasiatic languages spoken by indigenous Pearic peoples in parts of Cambodia and Thailand.
  • B. Hoyte
    Hoyte is the first name of Hoyte van Hoytema, a renowned Dutch-Swedish cinematographer known for his work on major films such as "Interstellar" and "Dunkirk."
  • C. Lontzen
    Lontzen is a municipality in eastern Belgium, located in the country’s German-speaking region near the border with Germany.
  • D. Owaneco
    Owaneco was a prominent Mohegan sachem (chief) known for his leadership and land dealings in colonial New England during the late 17th and early 18th centuries.
  • E. Pearce
    Pearce is a surname and given name of English origin, commonly considered a variant of "Pierce" and ultimately derived from the name "Peter."
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb300af2481908ae359972843c1ef completed March 7, 2026, 5:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbbcc5688190aad081dc8d119e7f completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:36 p.m.