Triple
T1835905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle orbiter |
E41065
|
entity |
| Predicate | reentryMethod |
P30129
|
FINISHED |
| Object | gliding unpowered 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: gliding unpowered reentry | Statement: [Space Shuttle orbiter, reentryMethod, gliding unpowered reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryMethod Context triple: [Space Shuttle orbiter, reentryMethod, gliding unpowered reentry]
-
A.
reentryProfile
chosen
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
B.
recoveryMethod
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
C.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
E.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.