Triple

T24158854
Position Surface form Disambiguated ID Type / Status
Subject 621st Contingency Response Wing E598772 entity
Predicate supportsGeographicScope P54919 FINISHED
Object global 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: global | Statement: [621st Contingency Response Wing, supportsGeographicScope, global]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsGeographicScope
Context triple: [621st Contingency Response Wing, supportsGeographicScope, global]
  • A. geographicScopeClaimed
    Indicates the geographic area or territory that an entity asserts or claims as being within its scope, authority, or coverage.
  • B. geographicConstraint
    Indicates a relationship where one entity’s existence, behavior, or validity is limited, restricted, or defined by specific geographic locations or boundaries.
  • C. geographicCoverageType
    Indicates the type or nature of the geographic area that something covers or applies to.
  • D. geographicAreaOfSupport chosen
    Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
  • E. geographicReception
    Indicates the geographic area or location where something (such as a work, message, or signal) is received, experienced, or has effect.
  • 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_69e288cb0a3081909ef221744f274384 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1e0e6d9fc8190a296f4f2b6d0d5e1 completed April 29, 2026, 10:43 a.m.
PD Predicate disambiguation batch_69f176585f3481909beb907de252cd98 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:31 p.m.