Triple
T23377816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makran subduction zone |
E593654
|
entity |
| Predicate | subductionRate |
P152499
|
FINISHED |
| Object | about 2–4 cm/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 2–4 cm/year | Statement: [Makran subduction zone, subductionRate, about 2–4 cm/year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subductionRate Context triple: [Makran subduction zone, subductionRate, about 2–4 cm/year]
-
A.
ageOfSubductingPlate
Indicates the age of a tectonic plate at the time and location where it is being subducted beneath another plate.
-
B.
subductionStyle
Indicates the manner or mode in which one tectonic plate descends beneath another at a convergent plate boundary.
-
C.
subductedDirection
Indicates the direction in which one tectonic plate moves beneath another during subduction.
-
D.
subductionRelated
Indicates a relationship in which one entity is associated with, caused by, or involved in the geological process of subduction.
-
E.
hasSubductingPlate
Indicates that one tectonic plate is moving beneath and being forced under another plate at a convergent plate boundary.
- F. None of above. chosen
Provenance (4 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b526ec8190b0304c72a9010abb |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:33 p.m.