Triple
T3474819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendocino Fracture Zone |
E73345
|
entity |
| Predicate | marksBoundaryIn |
P49185
|
FINISHED |
| Object | oceanic crust off northern California |
—
|
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: oceanic crust off northern California | Statement: [Mendocino Fracture Zone, marksBoundaryIn, oceanic crust off northern California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksBoundaryIn Context triple: [Mendocino Fracture Zone, marksBoundaryIn, oceanic crust off northern California]
-
A.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
B.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
D.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb580d4c819080bcc0bccd1e18e2 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.