Triple
T13456892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Fault |
E311258
|
entity |
| Predicate | isQuaternaryFault |
P109582
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Imperial Fault, isQuaternaryFault, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isQuaternaryFault Context triple: [Imperial Fault, isQuaternaryFault, true]
-
A.
isPartOfTectonicFeature
Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
-
B.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
C.
isFedByTectonicPlate
Indicates that something (such as a geological feature or process) receives material, energy, or influence from the movement or interaction of a specific tectonic plate.
-
D.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
E.
isQuadrangleOf
Indicates that one entity is a four-sided polygon (quadrilateral) that has the other entity as its defining instance or member.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0a75008190a508060c85f73604 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.