Triple
T34714448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn V first stage (S-IC) |
E1000732
|
entity |
| Predicate | separationVelocity |
P181806
|
FINISHED |
| Object | about 2.7 km/s |
—
|
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: about 2.7 km/s | Statement: [Saturn V first stage (S-IC), separationVelocity, about 2.7 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationVelocity Context triple: [Saturn V first stage (S-IC), separationVelocity, about 2.7 km/s]
-
A.
separationFromSpacecraft
Indicates that an object has detached or been released from a spacecraft, ending their physical or operational connection.
-
B.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
C.
separation
Indicates that one entity becomes or is kept apart from another entity or group, creating a distinct division or distance between them.
-
D.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
E.
knownSeparation
Indicates that a separation or split between entities is recognized or has been established as a known fact.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.