Triple
T2120811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonga-Kermadec subduction system |
E43916
|
entity |
| Predicate | HorizonDeepDepthApprox |
P16570
|
FINISHED |
| Object | about 10800 m |
—
|
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: about 10800 m | Statement: [Tonga-Kermadec subduction system, HorizonDeepDepthApprox, about 10800 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HorizonDeepDepthApprox Context triple: [Tonga-Kermadec subduction system, HorizonDeepDepthApprox, about 10800 m]
-
A.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
B.
depthMetresApprox
chosen
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
C.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
E.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
- 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_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. |
Created at: March 4, 2026, 7:44 p.m.