Triple
T9796399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India Plate |
E237727
|
entity |
| Predicate | velocity |
P13562
|
FINISHED |
| Object | about 4–5 cm per year northward relative to Eurasia |
—
|
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–5 cm per year northward relative to Eurasia | Statement: [India Plate, velocity, about 4–5 cm per year northward relative to Eurasia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: velocity Context triple: [India Plate, velocity, about 4–5 cm per year northward relative to Eurasia]
-
A.
speed
chosen
Indicates the rate at which an entity moves or changes position over time.
-
B.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
C.
vector
Indicates that one entity is a vector associated with, representing, or characterizing another entity (such as a quantity with magnitude and direction, or a carrier/representative of something).
-
D.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
E.
vorticity
Indicates the rotational motion or local spinning of a fluid element within a flow field.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34a53548190a8cb524381fe2bf9 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.