Triple
T33212370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEIS seismometer |
E850193
|
entity |
| Predicate | deployedOnSurfaceOf |
P56549
|
FINISHED |
| Object | Mars |
—
|
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: Mars | Statement: [SEIS seismometer, deployedOnSurfaceOf, Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deployedOnSurfaceOf Context triple: [SEIS seismometer, deployedOnSurfaceOf, Mars]
-
A.
visibleAtSurface
Indicates that something can be seen or is observable at the outer surface of an object or medium.
-
B.
collectedOnCelestialBody
Indicates that something (typically a sample or data) was gathered or obtained while located on a specific celestial body.
-
C.
locatedOnTerrain
chosen
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
D.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
E.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.