Triple
T7743628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solid Rocket Booster |
E175569
|
entity |
| Predicate | separatesAt |
P78452
|
FINISHED |
| Object | approximately two minutes after liftoff |
—
|
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: approximately two minutes after liftoff | Statement: [Solid Rocket Booster, separatesAt, approximately two minutes after liftoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesAt Context triple: [Solid Rocket Booster, separatesAt, approximately two minutes after liftoff]
-
A.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
D.
separatesPointsOn
Indicates that one entity divides or partitions a set or space such that distinct points lie on different sides or regions relative to it.
-
E.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:07 p.m.