Triple
T9634873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeeman slower |
E232902
|
entity |
| Predicate | inputVelocityRange |
P89377
|
FINISHED |
| Object | hundreds of meters per second |
—
|
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: hundreds of meters per second | Statement: [Zeeman slower, inputVelocityRange, hundreds of meters per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputVelocityRange Context triple: [Zeeman slower, inputVelocityRange, hundreds of meters per second]
-
A.
hasTypicalVelocity
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
B.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
C.
movementSpeed
Indicates the rate at which an entity changes its position over time.
-
D.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2a0e2c8190ab5aaa223b1e1cde |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:11 p.m.