Triple
T26295139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunda Strait islands |
E661392
|
entity |
| Predicate | nearSubductionZone |
P160213
|
FINISHED |
| Object | Sunda Trench |
—
|
NE NERFINISHED |
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: Sunda Trench | Statement: [Sunda Strait islands, nearSubductionZone, Sunda Trench]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearSubductionZone Context triple: [Sunda Strait islands, nearSubductionZone, Sunda Trench]
-
A.
subductionZoneName
Indicates the specific name assigned to a subduction zone where one tectonic plate is forced beneath another.
-
B.
affectsSubductionZone
Indicates that one entity has an influence or impact on the behavior, characteristics, or dynamics of a subduction zone.
-
C.
hasSubductingPlate
Indicates that one tectonic plate is moving beneath and being forced under another plate at a convergent plate boundary.
-
D.
subductionRate
Indicates the rate at which one tectonic plate moves beneath another into the mantle along a subduction zone.
-
E.
subductionRelated
Indicates a relationship in which one entity is associated with, caused by, or involved in the geological process of subduction.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ead95e08190bff727f2dac46eea |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:11 p.m.