Triple
T19382238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Crater |
E484839
|
entity |
| Predicate | landingDateContext |
P18610
|
FINISHED |
| Object | Opportunity landed in January 2004 |
—
|
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: Opportunity landed in January 2004 | Statement: [Eagle Crater, landingDateContext, Opportunity landed in January 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingDateContext Context triple: [Eagle Crater, landingDateContext, Opportunity landed in January 2004]
-
A.
landingDate
chosen
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
listingDate
Indicates the date on which an item, property, or asset is first officially placed on the market or made publicly available as a listing.
-
D.
landingYear
Indicates the year in which a landing event (such as an arrival or touchdown) took place.
-
E.
occupationDate
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a6075a88190aed7afa3b8fd3021 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.