Triple

T4449779
Position Surface form Disambiguated ID Type / Status
Subject Submillimeter Array E96378 entity
Predicate hasMountType P2519 FINISHED
Object alt-azimuth mount 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: alt-azimuth mount | Statement: [Submillimeter Array, hasMountType, alt-azimuth mount]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMountType
Context triple: [Submillimeter Array, hasMountType, alt-azimuth mount]
  • A. hasMount
    Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
  • B. hasMountingFeature
    Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
  • C. haveType
    Indicates that an entity belongs to or is classified under a specified type or category.
  • D. mountType chosen
    Indicates the manner or configuration in which one object is mounted or attached to another.
  • E. hasMaterialType
    Indicates that something is composed of, made from, or characterized by a specific type of material.
  • 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_69b345415ba481908df738e7174448ba completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355d5975c8190bfe8a2d5d2dbf075 completed March 13, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69b34f62c180819097ced38da2052207 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:32 p.m.