Triple
T9571703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shackleton Fracture Zone |
E230936
|
entity |
| Predicate | oceanFloorExpression |
P4263
|
FINISHED |
| Object | bathymetric lineament |
—
|
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: bathymetric lineament | Statement: [Shackleton Fracture Zone, oceanFloorExpression, bathymetric lineament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanFloorExpression Context triple: [Shackleton Fracture Zone, oceanFloorExpression, bathymetric lineament]
-
A.
seafloorType
chosen
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
B.
representsOcean
Indicates that a geographic or political entity is bordered by, adjacent to, or otherwise directly associated with a particular ocean.
-
C.
oceanPresence
Indicates that an entity is located in, adjacent to, or significantly influenced by an ocean.
-
D.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
E.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998bf20881909fad48ecb16dfa31 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.