Triple

T1053380
Position Surface form Disambiguated ID Type / Status
Subject Boeing AH-64 Apache E22747 entity
Predicate combatRadius P19870 FINISHED
Object approximately 480 km with external tanks 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: approximately 480 km with external tanks | Statement: [Boeing AH-64 Apache, combatRadius, approximately 480 km with external tanks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatRadius
Context triple: [Boeing AH-64 Apache, combatRadius, approximately 480 km with external tanks]
  • A. ringRadius
    Indicates the size of a ring by specifying the distance from its center to its outer edge.
  • B. radiusOfSevereDestruction
    Indicates the distance from a central point within which damage or destruction is expected to be extremely severe.
  • C. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • D. hasMeanRadius
    Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
  • E. range_km chosen
    Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
  • 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_69a493da02e081908c13ff5e02a0fe7a completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8b644088190a1f0f00f97941298 completed March 1, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69a4b731e25c8190b5ea8466648c2c9a completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.