Triple
T12794457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJ-60A solid rocket booster |
E305853
|
entity |
| Predicate | typicalUsagePhase |
P106948
|
FINISHED |
| Object | first stage 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: first stage ascent | Statement: [AJ-60A solid rocket booster, typicalUsagePhase, first stage ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsagePhase Context triple: [AJ-60A solid rocket booster, typicalUsagePhase, first stage ascent]
-
A.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6ca0288190aba01735b71a01da |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.