Triple

T10212104
Position Surface form Disambiguated ID Type / Status
Subject Voyager 2 attitude control system E242352 entity
Predicate mustHandle P92740 FINISHED
Object weak solar illumination at large heliocentric distances 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: weak solar illumination at large heliocentric distances | Statement: [Voyager 2 attitude control system, mustHandle, weak solar illumination at large heliocentric distances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mustHandle
Context triple: [Voyager 2 attitude control system, mustHandle, weak solar illumination at large heliocentric distances]
  • A. mustTouch
    Indicates that the entities are required to be in direct physical contact with each other.
  • B. mustGrant
    Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
  • C. mustMeet
    Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
  • D. mustFace
    Indicates that one entity is required or obligated to orient or direct its front side toward another entity or reference point.
  • E. mustRespect
    Indicates that one entity is obligated to show respect or deference toward 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_69d381ae26c48190985abd0e25ee5d04 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d3aa23bce881909b5deac612ec22cb completed April 6, 2026, 12:42 p.m.
PD Predicate disambiguation batch_69d39559e5ac8190b88eca75956b7e6a completed April 6, 2026, 11:13 a.m.
PDg Predicate description generation batch_69d3aa208c248190a0fb186b106389f3 completed April 6, 2026, 12:42 p.m.
Created at: April 6, 2026, 11:02 a.m.