Triple
T34827451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna Ye-8 series |
E1003966
|
entity |
| Predicate | firstSuccessfulRoverDelivery |
P91635
|
FINISHED |
| Object | Luna 17 |
E321813
|
NE 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: Luna 17 | Statement: [Luna Ye-8 series, firstSuccessfulRoverDelivery, Luna 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulRoverDelivery Context triple: [Luna Ye-8 series, firstSuccessfulRoverDelivery, Luna 17]
-
A.
firstSuccessfulMarsLanderProgram
Indicates that the subject is the space program responsible for achieving the first successful landing on Mars.
-
B.
firstSuccessfulLander
Indicates that the subject entity is the earliest one to have successfully landed on the specified target or within the given context.
-
C.
firstRover
chosen
Indicates that the subject is the first rover (e.g., chronologically or in sequence) relative to other rovers in a given context.
-
D.
roverMission
Indicates a mission undertaken by a rover, typically involving its deployment to explore, observe, or operate in a specific environment or target location.
-
E.
firstOperationDateOnMars
Indicates the date on which the very first operation or activity was carried out on Mars.
- F. None of above.
Provenance (4 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803ec4dc481909c590ea58bbfecbe |
completed | June 21, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.