Triple
T427415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 10 |
E9637
|
entity |
| Predicate | scientificInstruments |
P13781
|
FINISHED |
| Object | imaging photopolarimeter |
—
|
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: imaging photopolarimeter | Statement: [Pioneer 10, scientificInstruments, imaging photopolarimeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificInstruments Context triple: [Pioneer 10, scientificInstruments, imaging photopolarimeter]
-
A.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
B.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
C.
observatoryComplex
Indicates a relationship where multiple observatory-related facilities or structures are grouped together as parts of a single, integrated observatory complex.
-
D.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
E.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eed7f3508190995dcd39586ed614 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb93584819082f23eff13e17c4f |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.