Triple
T10197021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Near Infrared Camera and Multi-Object Spectrometer |
E238787
|
entity |
| Predicate | originalCoolant |
P10369
|
FINISHED |
| Object | solid nitrogen |
—
|
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: solid nitrogen | Statement: [Near Infrared Camera and Multi-Object Spectrometer, originalCoolant, solid nitrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCoolant Context triple: [Near Infrared Camera and Multi-Object Spectrometer, originalCoolant, solid nitrogen]
-
A.
coolant
chosen
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
B.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
C.
coolantLossOccurred
Indicates that a loss of coolant has taken place in the system or component in question.
-
D.
hasCoolingFlow
Indicates that an entity is equipped with or utilizes a system or mechanism to remove heat or maintain a lower temperature through the flow of a cooling medium.
-
E.
originallyBuiltUnder
Indicates that something was first constructed during the rule, authority, or administration of a particular person, group, or regime.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedcaf6688190938d8e56e29493eb |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.