Triple

T7409713
Position Surface form Disambiguated ID Type / Status
Subject menceyato E170968 entity
Predicate hasMilitaryOrganization P22805 FINISHED
Object war bands under the mencey 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: war bands under the mencey | Statement: [menceyato, hasMilitaryOrganization, war bands under the mencey]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMilitaryOrganization
Context triple: [menceyato, hasMilitaryOrganization, war bands under the mencey]
  • A. militaryOrganization
    Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
  • B. hasMilitaryAssociation chosen
    Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
  • C. hasMilitaryDivision
    Indicates that an entity possesses, includes, or is organizationally associated with a specific military division.
  • D. hasMilitaryBranch
    Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
  • E. militaryBranchComponentOf
    Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
  • 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_69c68a6010108190925e5284de022660 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f29d77848190a6170eb25483224f completed March 27, 2026, 9:11 p.m.
PD Predicate disambiguation batch_69c6f0323b2c819098ab72c33e6d8534 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:10 p.m.