Triple
T13538614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPE (Power and Propulsion Element) |
E323323
|
entity |
| Predicate | locationAfterLaunch |
P42649
|
FINISHED |
| Object | cislunar space |
—
|
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: cislunar space | Statement: [PPE (Power and Propulsion Element), locationAfterLaunch, cislunar space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationAfterLaunch Context triple: [PPE (Power and Propulsion Element), locationAfterLaunch, cislunar space]
-
A.
launchLocation
Indicates the place or site from which something is launched or set into motion.
-
B.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
-
C.
laterLocation
chosen
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
D.
locationAfterConversion
Indicates the place or position an entity occupies after it has been transformed, converted, or changed from one state or form to another.
-
E.
landingAfterAction
Indicates that one entity performs a landing event that occurs after a specified preceding action has taken place.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.