Triple
T4065870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAM |
E86320
|
entity |
| Predicate | locationOnRover |
P41222
|
FINISHED |
| Object | inside Curiosity rover body |
—
|
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: inside Curiosity rover body | Statement: [SAM, locationOnRover, inside Curiosity rover body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnRover Context triple: [SAM, locationOnRover, inside Curiosity rover body]
-
A.
locationOnSpacecraft
chosen
Indicates that one entity occupies or is situated at a specific place or position on a spacecraft.
-
B.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
C.
locationGroundSegment
Indicates that one entity is located at or associated with a specific ground segment or ground-based infrastructure.
-
D.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
E.
radarLocation
Indicates the geographic position where a radar system is installed or operating.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf58d9c8190936e453b0d397cb0 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.