Triple
T33644671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banda region |
E861925
|
entity |
| Predicate | interactsWithPlate |
P195362
|
FINISHED |
| Object | Australian 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: Australian Plate | Statement: [Banda region, interactsWithPlate, Australian Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactsWithPlate Context triple: [Banda region, interactsWithPlate, Australian Plate]
-
A.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
B.
onPlate
Indicates that one entity is physically resting atop and supported by the surface of a plate.
-
C.
plateInteraction
Indicates an interaction involving a plate, such as using, handling, or otherwise engaging with it in a specific context.
-
D.
adjacentToPlate
Indicates that one object is positioned directly next to or beside a plate without any significant separation.
-
E.
hasMicroplate
Indicates that an entity possesses or is associated with a specific microplate.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:42 a.m.