Triple
T518958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bouvet Triple Junction region |
E10770
|
entity |
| Predicate | hasPlateBoundaryType |
P1972
|
FINISHED |
| Object | mid-ocean ridge |
—
|
LITERAL FINISHED |
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: mid-ocean ridge | Statement: [Bouvet Triple Junction region, hasPlateBoundaryType, mid-ocean ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlateBoundaryType Context triple: [Bouvet Triple Junction region, hasPlateBoundaryType, mid-ocean ridge]
-
A.
plateBoundaryTypeWithCocosPlate
Indicates the type of tectonic plate boundary involving the Cocos Plate in a given plate interaction.
-
B.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
D.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
E.
plateBoundaryTypeWithPacificPlate
Indicates the type of tectonic plate boundary associated with the Pacific Plate in a given plate-boundary relationship.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f016ba5c81909825b04e7525b4ab |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.