Triple

T21979690
Position Surface form Disambiguated ID Type / Status
Subject Battle of Ninh Binh E542802 entity
Predicate region P40 FINISHED
Object Tonkin 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: Tonkin | Statement: [Battle of Ninh Binh, region, Tonkin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tonkin
Context triple: [Battle of Ninh Binh, region, Tonkin]
  • A. Tonkin chosen
    Tonkin was a historical region in northern Vietnam, centered around Hanoi, that became a French protectorate and key part of colonial French Indochina.
  • B. Cochinchina
    Cochinchina was the southern region of Vietnam that became a French colony and later formed part of French Indochina.
  • C. Annam
    Annam was a historical region in central Vietnam that served as a key center of resistance and revolutionary activity during the August General Uprising against French colonial rule.
  • D. Chau Doc
    Chau Doc is a riverfront city in Vietnam’s An Giang Province, known as a cultural crossroads near the Cambodian border and a gateway to the Mekong Delta.
  • E. Ba-Vi
    Ba-Vi is an entity known primarily by this single name, with no widely documented additional context or attributes.
  • 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_69e0c48070988190909db97667b9a0ac completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1248bdd88819098bfeca550608f14 completed April 28, 2026, 9:20 p.m.
Created at: April 16, 2026, 8:03 p.m.