Triple
T18771887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkib |
E459033
|
entity |
| Predicate | rotationalVelocity_kmPerS |
P69907
|
FINISHED |
| Object | about 200 |
—
|
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 200 | Statement: [Menkib, rotationalVelocity_kmPerS, about 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalVelocity_kmPerS Context triple: [Menkib, rotationalVelocity_kmPerS, about 200]
-
A.
hasRotationalVelocityKmPerSec
chosen
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
B.
equatorialLinearSpeed
Indicates the linear (tangential) speed of a rotating body measured specifically at its equator.
-
C.
hasRadialVelocity_km_per_s
Indicates that one entity has a measured radial velocity, expressed in kilometers per second, relative to another reference frame or object.
-
D.
averageOrbitalSpeed
Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
-
E.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.