Triple
T2861413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Canyon |
E63330
|
entity |
| Predicate | isDeeplyIncisedInto |
P40987
|
FINISHED |
| Object | Gulf of Mexico seafloor |
—
|
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: Gulf of Mexico seafloor | Statement: [Mississippi Canyon, isDeeplyIncisedInto, Gulf of Mexico seafloor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeeplyIncisedInto Context triple: [Mississippi Canyon, isDeeplyIncisedInto, Gulf of Mexico seafloor]
-
A.
carvedInto
chosen
Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
-
B.
impregnatedBy
Indicates that one entity has caused another entity to become pregnant.
-
C.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
isSpurOf
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary entity.
-
E.
isSeeOf
Indicates that one entity serves as the episcopal or ecclesiastical seat (see) of another, typically a bishop or similar religious office.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8df8288190816767169ea7cbf9 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.