Triple
T26726749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMU |
E673855
|
entity |
| Predicate | maxTranslationVelocity |
P2096
|
FINISHED |
| Object | about 25 feet 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: about 25 feet per second | Statement: [MMU, maxTranslationVelocity, about 25 feet per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTranslationVelocity Context triple: [MMU, maxTranslationVelocity, about 25 feet per second]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
maximumSlip
Indicates the greatest allowable or observed amount of slip between two contacting or interacting elements in a system.
-
C.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
D.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
E.
inputVelocityRange
Indicates that an entity’s input is valid only when its velocity falls within a specified numerical range.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6180b31f881909f532141eaf7896d |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:43 a.m.