Triple
T15085623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus submarine fan |
E360263
|
entity |
| Predicate | depositedOn |
P117246
|
FINISHED |
| Object | oceanic crust of the Arabian Sea |
—
|
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 of the Arabian Sea | Statement: [Indus submarine fan, depositedOn, oceanic crust of the Arabian Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositedOn Context triple: [Indus submarine fan, depositedOn, oceanic crust of the Arabian Sea]
-
A.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
-
B.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
-
C.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
D.
withdrawalDate
Indicates the date on which a withdrawal action occurs or is recorded.
-
E.
legalDepositSince
Indicates that a legal deposit obligation or status has been in effect for the subject entity continuously since the specified date.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00275cfa88190a13fe20b585d9fcb |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.