Triple
T318638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Australian Plate |
E7763
|
entity |
| Predicate | motionSpeed |
P2060
|
FINISHED |
| Object | about 5 to 7 centimeters per year |
—
|
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 5 to 7 centimeters per year | Statement: [Indo-Australian Plate, motionSpeed, about 5 to 7 centimeters per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionSpeed Context triple: [Indo-Australian Plate, motionSpeed, about 5 to 7 centimeters per year]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
hasAverageSurfaceSpeed
chosen
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
E.
clockSpeed
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e94513ec819089f5177f7a521e65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.