Triple
T430468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanche Fracture Zone |
E9699
|
entity |
| Predicate | displacementType |
P7348
|
FINISHED |
| Object | strike-slip |
—
|
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: strike-slip | Statement: [Romanche Fracture Zone, displacementType, strike-slip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementType Context triple: [Romanche Fracture Zone, displacementType, strike-slip]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
C.
relativeMotionType
chosen
Indicates the type or nature of motion occurring between two entities relative to one another.
-
D.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
E.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.