Triple
T36064510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 15 |
E1043182
|
entity |
| Predicate | intendedReturn |
P195745
|
FINISHED |
| Object | lunar soil capsule to Earth |
—
|
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: lunar soil capsule to Earth | Statement: [Luna 15, intendedReturn, lunar soil capsule to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReturn Context triple: [Luna 15, intendedReturn, lunar soil capsule to Earth]
-
A.
intendedReturnOfCharacter
Indicates that one entity is the planned or expected destination, place, or state to which a character is meant to return.
-
B.
returnIn
Indicates that an entity is brought, sent, or taken back to a prior location, state, or owner.
-
C.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
D.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
E.
intendedJumpType
Indicates the specific type or category of jump that is planned or intended to be performed.
- F. None of above. chosen
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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:08 p.m.