Triple
T37418614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way bulge and bar |
E929784
|
entity |
| Predicate | patternSpeed |
P188059
|
FINISHED |
| Object | of order 30–60 km/s/kpc |
—
|
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: of order 30–60 km/s/kpc | Statement: [Milky Way bulge and bar, patternSpeed, of order 30–60 km/s/kpc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternSpeed Context triple: [Milky Way bulge and bar, patternSpeed, of order 30–60 km/s/kpc]
-
A.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
racePattern
Indicates a recurring or characteristic way in which a race or competition unfolds, such as its typical pace, strategy, or sequence of events.
-
C.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
-
D.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
E.
speedDescribedAs
Indicates that one entity characterizes or labels the speed of another entity using a particular description or term.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.