Triple
T36485128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus |
E898914
|
entity |
| Predicate | reentryUse |
P185582
|
FINISHED |
| Object | waste incineration in Earth’s atmosphere |
—
|
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: waste incineration in Earth’s atmosphere | Statement: [Cygnus, reentryUse, waste incineration in Earth’s atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryUse Context triple: [Cygnus, reentryUse, waste incineration in Earth’s atmosphere]
-
A.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
B.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
C.
reentryConcern
Indicates a concern or issue related to an entity’s return or reentry into a system, environment, or context after having been outside it.
-
D.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
E.
reentryModule
Indicates that one entity serves as the reentry module or component used for returning from space or a high-altitude environment.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.