Triple

T31762688
Position Surface form Disambiguated ID Type / Status
Subject 369th Infantry Regiment E810722 entity
Predicate musicalUnit P130983 FINISHED
Object 369th Regimental Band 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: 369th Regimental Band | Statement: [369th Infantry Regiment, musicalUnit, 369th Regimental Band]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: musicalUnit
Context triple: [369th Infantry Regiment, musicalUnit, 369th Regimental Band]
  • A. musicalAct
    Indicates that one entity is a musical performer or group responsible for creating, performing, or being associated with the other entity (such as a song, album, or event).
  • B. notableUserUnit
    Indicates that a particular user is distinguished or recognized as notable within a given unit, group, or context.
  • C. musicGroupFormedPartOf
    Indicates that one musical group was formed as a component, subdivision, or offshoot of another musical group.
  • D. musicalAssociation chosen
    Indicates a relationship where entities are connected through music, such as collaboration, influence, shared performance, or other musically relevant association.
  • E. musicGroupFormedBy
    Indicates that a musical group was created, established, or brought together by a specific person or 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_69f348e463e08190b902d4819195e1f0 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: April 30, 2026, 11:31 p.m.