Triple

T3491686
Position Surface form Disambiguated ID Type / Status
Subject Council of Chiefs (Mohawk) E73746 entity
Predicate legitimacySource P39443 FINISHED
Object customary law 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: customary law | Statement: [Council of Chiefs (Mohawk), legitimacySource, customary law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legitimacySource
Context triple: [Council of Chiefs (Mohawk), legitimacySource, customary law]
  • A. authorityLegitimacyBasis chosen
    Indicates the foundational source or justification that makes an authority’s power or right to rule recognized as valid or legitimate.
  • B. legitimizedBy
    Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
  • C. legislationSource
    Indicates that one entity serves as the originating authority, basis, or source for a particular piece of legislation or legal rule.
  • D. legitimacyPerception
    Indicates how legitimate or appropriate an entity, action, or authority is perceived to be by relevant observers or stakeholders.
  • E. helpedLegitimize
    Indicates that one entity’s actions or support contributed to making another entity appear more credible, acceptable, or officially recognized.
  • 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_69ad85cca8d4819088494e9f3340fab5 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbbaa720c8190af47b052cc66c225 completed March 8, 2026, 6:10 p.m.
PD Predicate disambiguation batch_69adae0b34908190b2bb5766a2231f7a completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:18 p.m.