Triple

T17589032
Position Surface form Disambiguated ID Type / Status
Subject Very Large Array E428395 entity
Predicate arrayConfigurations P128122 FINISHED
Object A configuration 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: A configuration | Statement: [Very Large Array, arrayConfigurations, A configuration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: arrayConfigurations
Context triple: [Very Large Array, arrayConfigurations, A configuration]
  • A. numberOfConfigurations
    Indicates the total count of distinct configurations associated with or applicable to a given entity or situation.
  • B. featuresStringArrangementBy
    Indicates that something presents or includes a specific arrangement or ordering of strings that is determined or provided by a particular agent or source.
  • C. availableDisplaySizes
    Indicates the set of display size options that can be provided or used for a given entity.
  • D. aircraftConfiguration
    Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
  • E. displayConfiguration
    Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
  • F. None of above. chosen

Provenance (4 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469e50a80819098920d9190c30225 completed April 19, 2026, 5:36 a.m.
PD Predicate disambiguation batch_69e3b4fff0348190b899a32da537eaca completed April 18, 2026, 4:44 p.m.
PDg Predicate description generation batch_69e3bbb50b448190a59dd4be33c76db7 completed April 18, 2026, 5:13 p.m.
Created at: April 10, 2026, 5:51 a.m.