Triple
T5860714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kula Plate |
E130267
|
entity |
| Predicate | ceasedSubductionBy |
P67540
|
FINISHED |
| Object | Eocene |
—
|
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: Eocene | Statement: [Kula Plate, ceasedSubductionBy, Eocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedSubductionBy Context triple: [Kula Plate, ceasedSubductionBy, Eocene]
-
A.
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.
-
B.
subductionRelated
Indicates a relationship in which one entity is associated with, caused by, or involved in the geological process of subduction.
-
C.
subductsBeneath
Indicates that one entity moves downward and underneath another, typically as part of a convergent or overriding interaction.
-
D.
subductedDirection
Indicates the direction in which one tectonic plate moves beneath another during 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:56 p.m.