Triple
T8378768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA-20 |
E197637
|
entity |
| Predicate | instrument |
P792
|
FINISHED |
| Object | CrIS |
E197640
|
NE 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: CrIS | Statement: [NOAA-20, instrument, CrIS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CrIS Context triple: [NOAA-20, instrument, CrIS]
-
A.
CrIS
chosen
CrIS is a hyperspectral infrared sounder instrument used on NOAA’s Joint Polar Satellite System satellites to measure atmospheric temperature, moisture, and trace gases for weather forecasting and climate monitoring.
-
B.
CRIS
CRIS is a 32-bit embedded microprocessor architecture developed by Axis Communications, primarily used in their network devices and routers.
-
C.
CRUI
CRUI is the Conference of Italian University Rectors, a national association representing and coordinating the leadership of Italian universities.
-
D.
CRI
CRI is the three-letter ISO 3166-1 alpha-3 country code assigned to Costa Rica.
-
E.
CRI
CRI is a Kubernetes plugin interface that standardizes how container runtimes integrate with the Kubernetes kubelet to manage containers and pods.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c3dc1881908081c6a2829deb5a |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde7fa87908190a504f8aaae125a7a |
completed | April 2, 2026, 3:52 a.m. |
Created at: March 30, 2026, 6:02 p.m.