Triple
T16336477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISM |
E396690
|
entity |
| Predicate | stereoCapability |
P123005
|
FINISHED |
| Object | along-track stereo imaging |
—
|
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: along-track stereo imaging | Statement: [PRISM, stereoCapability, along-track stereo imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stereoCapability Context triple: [PRISM, stereoCapability, along-track stereo imaging]
-
A.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
B.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
C.
supportsStereoFMRadio
Indicates that the subject device is capable of receiving and playing stereo FM radio broadcasts.
-
D.
supportsAudioReturnChannel
Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
-
E.
supportsSpatialAudioWith
Indicates that one entity is compatible with and can provide or enable spatial audio functionality when used with 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.