Triple
T250712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horizon Deep |
E5139
|
entity |
| Predicate | depthClassification |
P6736
|
FINISHED |
| Object | hadal zone |
—
|
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: hadal zone | Statement: [Horizon Deep, depthClassification, hadal zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthClassification Context triple: [Horizon Deep, depthClassification, hadal zone]
-
A.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
B.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
C.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
E.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.