Triple
T36574297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble attitude control electronics |
E902201
|
entity |
| Predicate | sendsTelemetryTo |
P40250
|
FINISHED |
| Object | Hubble data handling system |
—
|
NE NERFINISHED |
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: Hubble data handling system | Statement: [Hubble attitude control electronics, sendsTelemetryTo, Hubble data handling system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sendsTelemetryTo Context triple: [Hubble attitude control electronics, sendsTelemetryTo, Hubble data handling system]
-
A.
telemetry
Indicates the collection, transmission, and recording of data about an entity’s state or behavior, typically from a remote or running system to a monitoring or analysis service.
-
B.
telemetryFrequency
Indicates how often telemetry data is collected, transmitted, or reported over time.
-
C.
hasSurveyTelescope
Indicates that an entity possesses or is equipped with a survey telescope used for wide-area observational surveys.
-
D.
communicatesTo
chosen
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
sendsLeaderTo
Indicates that one entity dispatches or assigns a leader to another entity or location.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.