Triple
T2321613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca Ridge |
E51192
|
entity |
| Predicate | isOverlainBy |
P27354
|
FINISHED |
| Object | marine sediments |
—
|
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: marine sediments | Statement: [Nazca Ridge, isOverlainBy, marine sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOverlainBy Context triple: [Nazca Ridge, isOverlainBy, marine sediments]
-
A.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
-
B.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
C.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
D.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
E.
hasSuperstrate
chosen
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.