Triple
T26726750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMU |
E673855
|
entity |
| Predicate | maxRotationRate |
P99987
|
FINISHED |
| Object | about 4 degrees 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 4 degrees per second | Statement: [MMU, maxRotationRate, about 4 degrees per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxRotationRate Context triple: [MMU, maxRotationRate, about 4 degrees per second]
-
A.
maxVerticalAngle
Indicates the greatest vertical angular difference or tilt between two entities or directions.
-
B.
hasRotationFrequency
chosen
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
C.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
D.
hasRotationalVelocityKmPerSec
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
E.
isRapidlyRotating
Indicates that an entity is spinning or rotating at a very high angular speed relative to a typical or reference rate.
- 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.