Triple
T29010063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panthalassa Ocean |
E736538
|
entity |
| Predicate | hadSubductionZones |
P39077
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Panthalassa Ocean, hadSubductionZones, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSubductionZones Context triple: [Panthalassa Ocean, hadSubductionZones, true]
-
A.
hasSubductingPlate
Indicates that one tectonic plate is moving beneath and being forced under another plate at a convergent plate boundary.
-
B.
nearSubductionZone
Indicates that one entity is located geographically close to a tectonic subduction zone.
-
C.
affectsSubductionZone
Indicates that one entity has an influence or impact on the behavior, characteristics, or dynamics of a subduction zone.
-
D.
subductionRelated
chosen
Indicates a relationship in which one entity is associated with, caused by, or involved in the geological process of subduction.
-
E.
largelySubductedBy
Indicates that one entity has been mostly or predominantly forced beneath another entity, as in a subduction process where the first is largely overridden or consumed by the second.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdb92508190bd0e7fe7877cdae2 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:41 a.m.