Triple
T2120812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonga-Kermadec subduction system |
E43916
|
entity |
| Predicate | oneOfWorlds |
P34966
|
FINISHED |
| Object | deepest ocean trenches |
—
|
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 ocean trenches | Statement: [Tonga-Kermadec subduction system, oneOfWorlds, deepest ocean trenches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfWorlds Context triple: [Tonga-Kermadec subduction system, oneOfWorlds, deepest ocean trenches]
-
A.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
B.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
C.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
D.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
E.
highestWorld
Indicates that the subject entity occupies or is associated with the topmost or most elevated world, level, or realm within a defined hierarchy of worlds.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3404348190bc843022fbd2b4d0 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:44 p.m.