Triple
T5489915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilkinson Basin |
E123674
|
entity |
| Predicate | namedFeatureType |
P5048
|
FINISHED |
| Object | undersea basin |
—
|
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: undersea basin | Statement: [Wilkinson Basin, namedFeatureType, undersea basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedFeatureType Context triple: [Wilkinson Basin, namedFeatureType, undersea basin]
-
A.
featureType
chosen
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.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
D.
USGSFeatureClass
Indicates a classification relationship where a geographic feature is assigned a specific feature class category as defined by the U.S. Geological Survey.
-
E.
nestFeature
Indicates that one entity is a structural or functional component contained within, or forming part of, another entity.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.