Triple
T17762496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Atlantic Ocean |
E443412
|
entity |
| Predicate | hasOceanFloorType |
P4263
|
FINISHED |
| Object | oceanic crust |
—
|
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: oceanic crust | Statement: [Central Atlantic Ocean, hasOceanFloorType, oceanic crust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOceanFloorType Context triple: [Central Atlantic Ocean, hasOceanFloorType, oceanic crust]
-
A.
hasOceanType
Indicates that a body of water is classified as belonging to a particular type of ocean or oceanic category.
-
B.
seafloorType
chosen
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
C.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
D.
hasOceanicCrustAlong
Indicates that an entity possesses or is characterized by oceanic crust extending along a specified boundary, feature, or region.
-
E.
hasOceanTrench
Indicates that a body of water contains or is associated with a specific ocean trench within its area.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485f887ac81908c896a50175692b9 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:11 a.m.