Triple
T30397141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendale Fault |
E773248
|
entity |
| Predicate | producedEffect |
P106972
|
FINISHED |
| Object | ground deformation |
—
|
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: ground deformation | Statement: [Greendale Fault, producedEffect, ground deformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedEffect Context triple: [Greendale Fault, producedEffect, ground deformation]
-
A.
providesEffect
chosen
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
B.
measuredEffect
Indicates that an action or process has produced a specific, quantified outcome or impact on something.
-
C.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
D.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
E.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 29, 2026, 8:03 p.m.