Triple

T13979678
Position Surface form Disambiguated ID Type / Status
Subject Echo Company, 2nd Battalion, 4th Marines E336274 entity
Predicate typicalSubunitOf P112029 FINISHED
Object infantry battalion 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: infantry battalion | Statement: [Echo Company, 2nd Battalion, 4th Marines, typicalSubunitOf, infantry battalion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSubunitOf
Context triple: [Echo Company, 2nd Battalion, 4th Marines, typicalSubunitOf, infantry battalion]
  • A. subunitOf
    Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
  • B. subunitType
    Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
  • C. typicalUnitType
    Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
  • D. formerSubunit
    Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
  • E. subsidiaryUnit
    Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
  • F. None of above. chosen

Provenance (4 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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e9fc7248190a9f26e253286ac3c completed April 14, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69dd465a21408190b912a42c50ffa0d9 completed April 13, 2026, 7:39 p.m.
PDg Predicate description generation batch_69de01ed2098819088ec45069f6f2609 completed April 14, 2026, 8:59 a.m.
Created at: April 9, 2026, 10:18 p.m.