Triple
T29396432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific–Indo-Australian region |
E745513
|
entity |
| Predicate | hasInteractingPlate |
P195362
|
FINISHED |
| Object | Pacific 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: Pacific Plate | Statement: [Pacific–Indo-Australian region, hasInteractingPlate, Pacific Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteractingPlate Context triple: [Pacific–Indo-Australian region, hasInteractingPlate, Pacific Plate]
-
A.
interactsWithPlate
chosen
Indicates that one entity engages in a physical or functional interaction with a plate.
-
B.
plateInteraction
Indicates an interaction involving a plate, such as using, handling, or otherwise engaging with it in a specific context.
-
C.
hasInteractionMode
Indicates the way in which two entities engage or interact with each other, specifying the manner, channel, or pattern of their interaction.
-
D.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 28, 2026, 2:46 p.m.