Triple

T4449800
Position Surface form Disambiguated ID Type / Status
Subject Submillimeter Array E96378 entity
Predicate hasNotableResult P1706 FINISHED
Object high-resolution imaging of protoplanetary disks 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: high-resolution imaging of protoplanetary disks | Statement: [Submillimeter Array, hasNotableResult, high-resolution imaging of protoplanetary disks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableResult
Context triple: [Submillimeter Array, hasNotableResult, high-resolution imaging of protoplanetary disks]
  • A. hasNotablePerformance
    Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
  • B. hasNotableContender
    Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
  • C. notableOutcome chosen
    Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
  • D. hasNotableRace
    Indicates that an entity is associated with a race or competition that is considered notable or significant.
  • E. hasNotablePerformanceIn
    Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
  • 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.