Triple
T16431857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Sample Return campaign |
E399086
|
entity |
| Predicate | sampleAnalysisLocation |
P21652
|
FINISHED |
| Object | terrestrial laboratories |
—
|
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: terrestrial laboratories | Statement: [Mars Sample Return campaign, sampleAnalysisLocation, terrestrial laboratories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleAnalysisLocation Context triple: [Mars Sample Return campaign, sampleAnalysisLocation, terrestrial laboratories]
-
A.
testLocation
chosen
Indicates the place or environment where a test, examination, or experimental procedure is conducted.
-
B.
AVALocation
Indicates that an entity’s location is specified or associated with a particular place or spatial position.
-
C.
dataCollectionLocation
Indicates the place or setting where data is gathered, recorded, or measured.
-
D.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
E.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9dffe48190a23852f828af55d8 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.