Triple
T33747304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Roller |
E864732
|
entity |
| Predicate | hasRotationTime |
P99987
|
FINISHED |
| Object | 30 minutes per revolution |
—
|
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: 30 minutes per revolution | Statement: [High Roller, hasRotationTime, 30 minutes per revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotationTime Context triple: [High Roller, hasRotationTime, 30 minutes per revolution]
-
A.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
B.
hasRotationFrequency
chosen
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
C.
hasRotationCharacteristic
Indicates that one entity possesses a specific rotational property, behavior, or attribute in relation to another entity or reference frame.
-
D.
swingSpanRotationTime
Indicates the amount of time required for a swing span (such as a rotating bridge section) to complete its rotational movement from one position to another.
-
E.
hasRotationalLag
Indicates that one entity rotates with a delay or phase offset relative to another entity’s rotation.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:45 a.m.