Triple
T6727248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 11 |
E153546
|
entity |
| Predicate | landingAttempted |
P37029
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Luna 11, landingAttempted, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingAttempted Context triple: [Luna 11, landingAttempted, no]
-
A.
landingAttemptResult
Indicates the outcome or status of an attempted landing action, such as whether the landing succeeded, failed, or had another specific result.
-
B.
landingSiteAttempt
chosen
Indicates an attempt by an entity to use or reach a particular location as a landing site, regardless of whether the landing ultimately succeeds.
-
C.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
D.
landingSuccess
Indicates that an attempted landing action has been completed successfully.
-
E.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.