Triple
T6297824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsili Seamount |
E141173
|
entity |
| Predicate | seaFloorProvince |
P70782
|
FINISHED |
| Object | Tyrrhenian back-arc 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: Tyrrhenian back-arc basin | Statement: [Marsili Seamount, seaFloorProvince, Tyrrhenian back-arc basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaFloorProvince Context triple: [Marsili Seamount, seaFloorProvince, Tyrrhenian back-arc basin]
-
A.
endSea
Indicates that something marks the boundary or termination point of a sea or sea area.
-
B.
seaConnection
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
C.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
D.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
-
E.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
- F. None of above. chosen
Provenance (4 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0643bd0748190af7abbebb6f94242 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c06284848c8190a0151ff3e8682889 |
completed | March 22, 2026, 9:43 p.m. |
Created at: March 22, 2026, 4:27 p.m.