Triple

T23061586
Position Surface form Disambiguated ID Type / Status
Subject Manide Agta E574315 entity
Predicate selfIdentification P4296 FINISHED
Object Manide 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: Manide | Statement: [Manide Agta, selfIdentification, Manide]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manide
Context triple: [Manide Agta, selfIdentification, Manide]
  • A. Manide chosen
    Manide is an endangered Austronesian language spoken by the Manide (Negrito) people in parts of southern Luzon in the Philippines.
  • B. Mandiyali
    Mandiyali is an Indo-Aryan language spoken primarily in the Mandi region of Himachal Pradesh, India.
  • C. Manay
    Manay is a coastal municipality in the province of Davao Oriental in the Philippines, known for its beaches and natural attractions.
  • D. Manhiça
    Manhiça is a town and district in southern Mozambique known for its agricultural activities and for hosting the prominent Manhiça Health Research Centre.
  • E. Manawan
    Manawan is an Atikamekw First Nations community located in the Mauricie region of Quebec, Canada.
  • 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_69e245ba7ae48190be606dbc54120e39 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1899ff96081908d89a07a3b1065c8 completed April 29, 2026, 4:31 a.m.
Created at: April 17, 2026, 3:55 p.m.