Triple
T18695657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crab Nebula |
E457107
|
entity |
| Predicate | expandsAtSpeed |
P14356
|
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: [Crab Nebula, expandsAtSpeed, about 1500 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsAtSpeed Context triple: [Crab Nebula, expandsAtSpeed, about 1500 km/s]
-
A.
expandedRapidly
Indicates that an entity’s size, scope, or intensity increased significantly within a short period of time.
-
B.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
C.
expands
chosen
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
D.
expandsTo
Indicates that one entity unfolds, develops, or is elaborated into another, typically more detailed or extensive, representation or form.
-
E.
expandsAccordingTo
Indicates that one entity increases in size, scope, or extent in a manner determined or governed by another specified factor, rule, or pattern.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.