Triple

T30658750
Position Surface form Disambiguated ID Type / Status
Subject Konyak Naga tribe E780462 entity
Predicate warriorSymbol P80953 FINISHED
Object facial and body tattoos LITERAL 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: facial and body tattoos | Statement: [Konyak Naga tribe, warriorSymbol, facial and body tattoos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: warriorSymbol
Context triple: [Konyak Naga tribe, warriorSymbol, facial and body tattoos]
  • A. protectiveEmblemName
    Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
  • B. recognizesAsWarrior
    Indicates that one entity acknowledges or accepts another entity as a warrior.
  • C. symbolicWeapon
    Indicates a relationship where something functions as a symbolic or emblematic weapon for an entity, representing power, threat, or conflict rather than serving as a literal physical armament.
  • D. ceremonialSymbol chosen
    Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
  • E. isWarHeroOf
    Indicates that one entity is recognized as a war hero in relation to, or on behalf of, another entity (such as a country, group, or cause).
  • 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_69f224a6d10481909290be1a00fc83b3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68adf0f908190aba108c90a766428 completed May 2, 2026, 11:38 p.m.
PD Predicate disambiguation batch_69f6861170d08190bb98be609d436f84 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:30 p.m.