Triple
T10783589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocos–Caribbean plate boundary |
E254391
|
entity |
| Predicate | lithosphereTypeSubducting |
P32326
|
FINISHED |
| Object | oceanic |
—
|
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: oceanic | Statement: [Cocos–Caribbean plate boundary, lithosphereTypeSubducting, oceanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lithosphereTypeSubducting Context triple: [Cocos–Caribbean plate boundary, lithosphereTypeSubducting, oceanic]
-
A.
crustTypeSubducting
chosen
Indicates that one type of crust is moving beneath another plate in a subduction process.
-
B.
hasSubductingPlate
Indicates that one tectonic plate is moving beneath and being forced under another plate at a convergent plate boundary.
-
C.
subductionStyle
Indicates the manner or mode in which one tectonic plate descends beneath another at a convergent plate boundary.
-
D.
subductionRelated
Indicates a relationship in which one entity is associated with, caused by, or involved in the geological process of subduction.
-
E.
ageOfSubductingPlate
Indicates the age of a tectonic plate at the time and location where it is being subducted beneath another plate.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.