Triple
T35506044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTRO-F |
E1026152
|
entity |
| Predicate | postHeliumPhase |
P5784
|
FINISHED |
| Object | warm mission with limited bands |
—
|
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: warm mission with limited bands | Statement: [ASTRO-F, postHeliumPhase, warm mission with limited bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postHeliumPhase Context triple: [ASTRO-F, postHeliumPhase, warm mission with limited bands]
-
A.
latestPhase
Indicates the most recent stage or step reached in a process, lifecycle, or sequence of phases.
-
B.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
C.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
D.
phase
chosen
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
E.
thrustPhase
Indicates a phase in which a propulsion system is actively producing thrust as part of a larger operation or trajectory.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.