Triple
T25096374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Kumamoto earthquakes |
E628599
|
entity |
| Predicate | occurredOnPlate |
P19446
|
FINISHED |
| Object | Amur 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: Amur Plate | Statement: [2016 Kumamoto earthquakes, occurredOnPlate, Amur Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredOnPlate Context triple: [2016 Kumamoto earthquakes, occurredOnPlate, Amur Plate]
-
A.
onPlate
Indicates that one entity is physically resting atop and supported by the surface of a plate.
-
B.
precededByOnPlate
Indicates that one item was placed or appeared on a plate earlier in time than another item.
-
C.
involvesPlate
chosen
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
D.
followedByOnPlate
Indicates that one item is positioned immediately after another item on the same plate, in a defined order or sequence.
-
E.
plate3
Indicates that one entity is a third plate or dish associated with, supporting, or serving another entity in a given context.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:25 a.m.