Triple
T250709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horizon Deep |
E5139
|
entity |
| Predicate | studiedFor |
P1945
|
FINISHED |
| Object | deep-sea geology |
—
|
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: deep-sea geology | Statement: [Horizon Deep, studiedFor, deep-sea geology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiedFor Context triple: [Horizon Deep, studiedFor, deep-sea geology]
-
A.
studiedUnder
Indicates that one entity received instruction, training, or mentorship from another, typically in an academic or apprenticeship context.
-
B.
studiedBy
chosen
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
C.
isStudiedIn
Indicates that a subject (such as a topic, field, or phenomenon) is examined, researched, or learned about within a particular context, environment, or discipline.
-
D.
hasLanguageOfStudy
Indicates that an entity studies or is engaged in learning a particular language.
-
E.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
- 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.