Triple
T29747944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanimbar Trough |
E752809
|
entity |
| Predicate | convergentBoundaryBetween |
P21873
|
FINISHED |
| Object | Indo-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: Indo-Australian Plate | Statement: [Tanimbar Trough, convergentBoundaryBetween, Indo-Australian Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convergentBoundaryBetween Context triple: [Tanimbar Trough, convergentBoundaryBetween, Indo-Australian Plate]
-
A.
plateBoundaryBetween
chosen
Indicates a geological relationship where a boundary exists between two tectonic plates.
-
B.
plateBoundarySegmentOf
Indicates that one tectonic plate boundary segment is a constituent part of, or lies along, a larger tectonic plate boundary.
-
C.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
D.
climateBoundaryBetween
Indicates a boundary or dividing line between two regions that differ in climate characteristics or classifications.
-
E.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 7:52 p.m.