Triple

T33431376
Position Surface form Disambiguated ID Type / Status
Subject 37th Training Support Squadron E856139 entity
Predicate parentInstallation P121557 FINISHED
Object Joint Base San Antonio 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: Joint Base San Antonio | Statement: [37th Training Support Squadron, parentInstallation, Joint Base San Antonio]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parentInstallation
Context triple: [37th Training Support Squadron, parentInstallation, Joint Base San Antonio]
  • A. associatedInstallation
    Indicates a relationship where one entity is linked to, or occurs in connection with, a particular installation (such as a facility, system, or setup) with which it is contextually or functionally related.
  • B. hasParentInstallation chosen
    Indicates that one installation is the parent or higher-level installation to which another installation belongs or from which it is derived.
  • C. intendedInstallation
    Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
  • D. includesInstallation
    Indicates that one entity comes with or provides the installation of another entity as part of its offering or package.
  • E. supportsInstallation
    Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another 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_69f349709e7881908c342b4d34f555f4 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
Created at: May 1, 2026, 1:36 a.m.