Triple
T2142425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kermadec Trench |
E46788
|
entity |
| Predicate | among |
P36577
|
FINISHED |
| Object | deepest oceanic trenches on Earth |
—
|
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: deepest oceanic trenches on Earth | Statement: [Kermadec Trench, among, deepest oceanic trenches on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: among Context triple: [Kermadec Trench, among, deepest oceanic trenches on Earth]
-
A.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
B.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
C.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
D.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:44 p.m.