Triple

T16396639
Position Surface form Disambiguated ID Type / Status
Subject 3/1 E398199 entity
Predicate hasComponent P35 FINISHED
Object Kilo Company E398202 NE 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: Kilo Company | Statement: [3/1, hasComponent, Kilo Company]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kilo Company
Context triple: [3/1, hasComponent, Kilo Company]
  • A. Kilo Company chosen
    Kilo Company is a rifle company within the U.S. Marine Corps’ 3rd Battalion, 1st Marines, known for its role in infantry combat operations.
  • B. F Company
    F Company is a rifle company within the U.S. Marine Corps’ 2nd Battalion, 4th Marines, known for its role in infantry combat operations.
  • C. Bobcat Company
    Bobcat Company is an American manufacturer best known for its compact construction and agricultural equipment, including skid-steer loaders and mini excavators.
  • D. 602 Commando Company
    602 Commando Company is an elite special operations unit of the Argentine Army known for its role in high-risk and unconventional warfare missions.
  • E. 601 Commando Company
    601 Commando Company is an elite special operations unit of the Argentine Army known for conducting high-risk commando and unconventional warfare missions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327cb3c708190b64341cb1410ed81 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00357838a88190be88c51f454be6eb completed May 10, 2026, 7:36 a.m.
Created at: April 10, 2026, 5:09 a.m.