Triple

T35688930
Position Surface form Disambiguated ID Type / Status
Subject Kachin conflict E1031233 entity
Predicate hasNegotiationParty P378 FINISHED
Object Kachin Independence Organization 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: Kachin Independence Organization | Statement: [Kachin conflict, hasNegotiationParty, Kachin Independence Organization]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNegotiationParty
Context triple: [Kachin conflict, hasNegotiationParty, Kachin Independence Organization]
  • A. negotiatingParty chosen
    Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
  • B. hasOtherParty
    Indicates that an entity is associated with another distinct party involved in the same relationship, transaction, or interaction.
  • C. hasNegotiationHistory
    Indicates that there has been one or more prior negotiation interactions or exchanges between the related entities.
  • D. hasNegotiationFormat
    Indicates that there is a specified structure, protocol, or method by which negotiation between parties is conducted.
  • E. negotiatedVia
    Indicates that an agreement, deal, or arrangement was reached through the use of a specific intermediary, channel, or method of negotiation.
  • F. None of above.

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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a0027e4a59481909417b2531daaf480 completed May 10, 2026, 6:38 a.m.
PD Predicate disambiguation batch_6a0026a42bc08190ad3322ce625a523a completed May 10, 2026, 6:33 a.m.
Created at: May 3, 2026, 4:05 p.m.