Triple
T5645045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIKE |
E124363
|
entity |
| Predicate | resolutionCapability |
P40836
|
FINISHED |
| Object | high spectral resolution |
—
|
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: high spectral resolution | Statement: [MIKE, resolutionCapability, high spectral resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionCapability Context triple: [MIKE, resolutionCapability, high spectral resolution]
-
A.
resolutionDevice
Indicates a device or instrument that is used to resolve, determine, or measure the outcome or value associated with another entity or process.
-
B.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
C.
displayCapabilities
Indicates the set of functions, features, or behaviors that an entity is able to present or support in a given context.
-
D.
sensorResolution
chosen
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
E.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a8eccc8190837d4705670dc25e |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.