Triple
T25750619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InSight |
E648459
|
entity |
| Predicate | SEISProvider |
P145807
|
FINISHED |
| Object | CNES |
—
|
NE NERFINISHED |
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: CNES | Statement: [InSight, SEISProvider, CNES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SEISProvider Context triple: [InSight, SEISProvider, CNES]
-
A.
seismicMonitoring
Indicates the ongoing observation and measurement of seismic activity or ground motion to detect, record, and analyze earthquakes or related geophysical events.
-
B.
seismicSetting
Indicates the geological or tectonic conditions under which seismic activity occurs or is characterized.
-
C.
seismologicalOrganization
chosen
Indicates that an entity is a seismological organization, i.e., an institution responsible for studying, monitoring, or reporting seismic activity.
-
D.
seismicEvent
Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
-
E.
seismicSignificance
Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7df2ac8190a206646c8640cec0 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:34 a.m.