Triple
T3894836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Septentrional-Oriente fault zone |
E88143
|
entity |
| Predicate | associatedProcess |
P5667
|
FINISHED |
| Object | earthquake generation |
—
|
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: earthquake generation | Statement: [Septentrional-Oriente fault zone, associatedProcess, earthquake generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedProcess Context triple: [Septentrional-Oriente fault zone, associatedProcess, earthquake generation]
-
A.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
B.
associatedOperation
chosen
Indicates that one entity is linked to or involved with a particular operation, process, or activity.
-
C.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
D.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
-
E.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.