Triple
T25753592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koryaksky–Avachinsky volcanic group |
E648529
|
entity |
| Predicate | formedBeneath |
P20246
|
FINISHED |
| Object | Okhotsk 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: Okhotsk Plate | Statement: [Koryaksky–Avachinsky volcanic group, formedBeneath, Okhotsk Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedBeneath Context triple: [Koryaksky–Avachinsky volcanic group, formedBeneath, Okhotsk Plate]
-
A.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds of another entity.
-
B.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
C.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
-
D.
under
chosen
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
E.
formedStable
Indicates that a relationship, structure, or configuration has come into existence and remains consistently intact or unchanged over time.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 22, 2026, 4:37 a.m.