Triple
T3592038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorda Ridge |
E76046
|
entity |
| Predicate | isStudiedUsing |
P49589
|
FINISHED |
| Object | seafloor mapping |
—
|
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: seafloor mapping | Statement: [Gorda Ridge, isStudiedUsing, seafloor mapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStudiedUsing Context triple: [Gorda Ridge, isStudiedUsing, seafloor mapping]
-
A.
studiedBy
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).
-
B.
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.
-
C.
hasSubjectOfStudy
Indicates that an entity (such as a person or organization) focuses on, researches, or specializes in a particular field or topic of study.
-
D.
hasLanguageOfStudy
Indicates that an entity studies or is engaged in learning a particular language.
-
E.
widelyStudiedIn
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.