Triple
T27356683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Flight Instrumentation |
E685703
|
entity |
| Predicate | monitoredPhase |
P162222
|
FINISHED |
| Object | ascent |
—
|
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: ascent | Statement: [Development Flight Instrumentation, monitoredPhase, ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoredPhase Context triple: [Development Flight Instrumentation, monitoredPhase, ascent]
-
A.
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.
-
B.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
C.
governancePhase
Indicates the specific stage or phase an entity is in within a broader governance or decision-making process.
-
D.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
E.
protocolPhase
Indicates the specific stage or step within a defined protocol or procedural sequence that an action, process, or entity is associated with.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c1dec70819087f3f891cb18d6f6 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:51 a.m.