Triple
T581473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca Ridge |
E15067
|
entity |
| Predicate | oceanicCrustFormation |
P7366
|
FINISHED |
| Object | site of seafloor spreading |
—
|
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: site of seafloor spreading | Statement: [Juan de Fuca Ridge, oceanicCrustFormation, site of seafloor spreading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanicCrustFormation Context triple: [Juan de Fuca Ridge, oceanicCrustFormation, site of seafloor spreading]
-
A.
seafloorSpreadingOccursAt
chosen
Indicates that the process of seafloor spreading takes place at a specified tectonic or oceanic location.
-
B.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
C.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
D.
subductionStyle
Indicates the manner or mode in which one tectonic plate descends beneath another at a convergent plate boundary.
-
E.
orogeny
Indicates the geological process by which mountain ranges are formed, typically through tectonic plate interactions such as collision, subduction, or compression.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b84899881909d5b2b4e67e22d9b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.