Triple
T2849352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis I |
E63054
|
entity |
| Predicate | reentryEnvironment |
P30129
|
FINISHED |
| Object | lunar-return high-energy reentry |
—
|
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-return high-energy reentry | Statement: [Artemis I, reentryEnvironment, lunar-return high-energy reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryEnvironment Context triple: [Artemis I, reentryEnvironment, lunar-return high-energy reentry]
-
A.
reentryProfile
chosen
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
B.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
C.
reentryBreakupLocation
Indicates the location where an object breaks up or disintegrates during its reentry into an atmosphere.
-
D.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
E.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.