Triple
T1019412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Pacific Rise |
E22005
|
entity |
| Predicate | hasSpreadingRate |
P2062
|
FINISHED |
| Object | relatively high |
—
|
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: relatively high | Statement: [East Pacific Rise, hasSpreadingRate, relatively high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpreadingRate Context triple: [East Pacific Rise, hasSpreadingRate, relatively high]
-
A.
spreadingRateType
chosen
Indicates the manner or category of how quickly or in what way something spreads or propagates.
-
B.
hasSpreadingCenter
Indicates that one geological or tectonic entity contains or is associated with a spreading center where crust is being created and plates diverge.
-
C.
averageSpreadingRate
Indicates the typical rate at which something (such as a phenomenon, substance, or influence) expands or propagates over a given distance or time.
-
D.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
E.
spreadTo
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dbcf7c8190858b2d16a27bd2ff |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.