Triple
T430460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanche Fracture Zone |
E9699
|
entity |
| Predicate | featureClass |
P9677
|
FINISHED |
| Object | submarine valley |
—
|
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: submarine valley | Statement: [Romanche Fracture Zone, featureClass, submarine valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureClass Context triple: [Romanche Fracture Zone, featureClass, submarine valley]
-
A.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
C.
featureOfInterest
Indicates the entity or object that is the primary subject or focus of the described observation, measurement, or analysis.
-
D.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
E.
GNISFeatureClass
chosen
Indicates the categorical type or class assigned to a geographic feature in the Geographic Names Information System (GNIS).
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.