Triple
T35003836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheba Ridge |
E1009754
|
entity |
| Predicate | earthScienceDiscipline |
P95928
|
FINISHED |
| Object | marine 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: marine geology | Statement: [Sheba Ridge, earthScienceDiscipline, marine geology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earthScienceDiscipline Context triple: [Sheba Ridge, earthScienceDiscipline, marine geology]
-
A.
geologicalStudyField
Indicates that a particular field or area is the subject or location of a geological study or investigation.
-
B.
geologyRelatedTo
chosen
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
-
C.
geologyStudiedBy
Indicates that a geological feature, subject, or area is the object of study or research conducted by a specified person or organization.
-
D.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
E.
earth
Indicates that an entity is the planet Earth or is located on, associated with, or pertaining to Earth.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.