Triple

T329915
Position Surface form Disambiguated ID Type / Status
Subject Ames Research Center 40-by-80-Foot Wind Tunnel E6602 entity
Predicate fanConfiguration P2093 FINISHED
Object propeller-driven fans 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: propeller-driven fans | Statement: [Ames Research Center 40-by-80-Foot Wind Tunnel, fanConfiguration, propeller-driven fans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fanConfiguration
Context triple: [Ames Research Center 40-by-80-Foot Wind Tunnel, fanConfiguration, propeller-driven fans]
  • A. fanBase
    Indicates that one entity is the group of admirers or supporters devoted to another entity.
  • B. fanbaseCharacteristic
    Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
  • C. fanBelief
    Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
  • D. fanChant
    Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
  • E. configuration chosen
    Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eaaeb64881909c7ab9bca3378e2b completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94aab1c8190b8654708c87eeb91 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.