Triple
T9837703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus XL |
E239143
|
entity |
| Predicate | stageSeparation |
P81466
|
FINISHED |
| Object | sequential solid-stage separation |
—
|
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: sequential solid-stage separation | Statement: [Pegasus XL, stageSeparation, sequential solid-stage separation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageSeparation Context triple: [Pegasus XL, stageSeparation, sequential solid-stage separation]
-
A.
stageAfter
Indicates that one stage occurs later in sequence or order than another specified stage.
-
B.
separationProcess
chosen
Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
E.
gradeSeparationProject
Indicates a project whose purpose is to separate different transportation routes or levels (such as roads and railways) so they no longer intersect at the same grade.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.