Triple
T18887514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 1 |
E461993
|
entity |
| Predicate | expansionVelocity |
P132322
|
FINISHED |
| Object | about 1500 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 1500 km/s | Statement: [Messier 1, expansionVelocity, about 1500 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionVelocity Context triple: [Messier 1, expansionVelocity, about 1500 km/s]
-
A.
nebulaExpansionVelocity
chosen
Indicates the speed at which a nebula is expanding outward from its center over time.
-
B.
stellarWindTerminalVelocity
Indicates the final, asymptotic speed reached by a star’s stellar wind far from the star, after it has been fully accelerated.
-
C.
meteorVelocity
Indicates the speed and direction at which a meteor is moving through space or an atmosphere.
-
D.
hasDetonationVelocity
Indicates the specific speed at which a material’s detonation wave propagates through it during an explosive reaction.
-
E.
nozzleExpansionRatio
Indicates the ratio between a nozzle’s exit area and its throat area, describing how much the flow expands as it passes through the nozzle.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c4777434819098850da0ee1c6b43 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.