Triple

T36296579
Position Surface form Disambiguated ID Type / Status
Subject 26th Infantry Brigade Combat Team E893385 entity
Predicate carriesLineageFrom P115355 FINISHED
Object 26th Infantry Division 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: 26th Infantry Division | Statement: [26th Infantry Brigade Combat Team, carriesLineageFrom, 26th Infantry Division]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: carriesLineageFrom
Context triple: [26th Infantry Brigade Combat Team, carriesLineageFrom, 26th Infantry Division]
  • A. sourceOfLineageFor chosen
    Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
  • B. hasLineageCharacteristic
    Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
  • C. basedOnCharacterLineage
    Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
  • D. impliesLineage
    Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
  • E. hasNotableLineageFor
    Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
  • 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_69f76e4a61f0819084a2b68dbbb4efc6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba6d06f48190a71b5a2f19e2232f completed May 3, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.