Triple
T13179578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infrared Astronomical Satellite |
E313687
|
entity |
| Predicate | hasOnboardInstrument |
P36407
|
FINISHED |
| Object | infrared photometer |
—
|
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: infrared photometer | Statement: [Infrared Astronomical Satellite, hasOnboardInstrument, infrared photometer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardInstrument Context triple: [Infrared Astronomical Satellite, hasOnboardInstrument, infrared photometer]
-
A.
hasOnboardFeature
chosen
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
B.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
C.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
hadInstrument
Indicates that an action or event was performed using a particular instrument or tool.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.