Triple
T34827458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna Ye-8 series |
E1003966
|
entity |
| Predicate | landerConfiguration |
P124736
|
FINISHED |
| Object | Ye-8 |
—
|
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: Ye-8 | Statement: [Luna Ye-8 series, landerConfiguration, Ye-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landerConfiguration Context triple: [Luna Ye-8 series, landerConfiguration, Ye-8]
-
A.
landerProvider
Indicates the organization or entity responsible for providing or operating the lander used in a mission or operation.
-
B.
landingConfiguration
chosen
Indicates the specific arrangement or setup used for an entity’s landing phase or landing operation.
-
C.
continentConfiguration
Indicates how landmasses and oceans are spatially arranged and distributed on a planet’s surface at a given time.
-
D.
landerFunction
Indicates that an entity serves the role or performs the function of a lander, typically designed to descend to and operate on the surface of a celestial body.
-
E.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.