Triple
T26170080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stardust |
E654375
|
entity |
| Predicate | sampleReturnCapsuleLandingRegion |
P54852
|
FINISHED |
| Object | Utah, United States |
—
|
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: Utah, United States | Statement: [Stardust, sampleReturnCapsuleLandingRegion, Utah, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleReturnCapsuleLandingRegion Context triple: [Stardust, sampleReturnCapsuleLandingRegion, Utah, United States]
-
A.
intendedLandingRegion
Indicates the geographic area or region where something is planned or expected to land.
-
B.
reentryCapsuleLandingCountry
chosen
Indicates the country where a spacecraft’s reentry capsule lands or is intended to land.
-
C.
lunarLandingRegion
Indicates the geographic region on the Moon where a spacecraft or mission has landed.
-
D.
partOfLandingSector
Indicates that one entity constitutes a component or subdivision within a larger landing sector.
-
E.
isMajorLandingRegion
Indicates that a location serves as a primary or significant area where landings (such as aircraft, spacecraft, or vessels) commonly occur.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 8:34 p.m.