Triple
T35003834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheba Ridge |
E1009754
|
entity |
| Predicate | crustProduction |
P181979
|
FINISHED |
| Object | creates new oceanic crust in Gulf of Aden |
—
|
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: creates new oceanic crust in Gulf of Aden | Statement: [Sheba Ridge, crustProduction, creates new oceanic crust in Gulf of Aden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crustProduction Context triple: [Sheba Ridge, crustProduction, creates new oceanic crust in Gulf of Aden]
-
A.
crustTypeProduced
Indicates the type of crust that is produced as the result of a particular process, action, or production activity.
-
B.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
C.
crustAppearance
Indicates the visual characteristics or look of a crust as perceived from its outer surface.
-
D.
hasCrust
Indicates that one entity possesses or is characterized by an outer crust layer.
-
E.
hasCrustBehavior
Indicates how the crust of an object or material behaves or responds under certain conditions or interactions.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.