Triple
T37530536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashitaka volcano |
E933027
|
entity |
| Predicate | underOverridingPlate |
P28043
|
FINISHED |
| Object | Eurasian Plate |
—
|
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: Eurasian Plate | Statement: [Ashitaka volcano, underOverridingPlate, Eurasian Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underOverridingPlate Context triple: [Ashitaka volcano, underOverridingPlate, Eurasian Plate]
-
A.
overridingPlate
Indicates that one plate or tectonic unit moves over and above another plate in a convergent or subduction-related setting.
-
B.
overridesPlate
Indicates that one plate or plating configuration replaces, supersedes, or takes precedence over another in a given context.
-
C.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
D.
onPlate
Indicates that one entity is physically resting atop and supported by the surface of a plate.
-
E.
tectonicPlateOverriding
chosen
Indicates that one tectonic plate is moving over and above another plate at a convergent boundary, overriding it in the subduction process.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:17 p.m.