Triple
T27116447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston Seismic Zone |
E686858
|
entity |
| Predicate | hasUncertainFaultGeometry |
P168938
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charleston Seismic Zone, hasUncertainFaultGeometry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainFaultGeometry Context triple: [Charleston Seismic Zone, hasUncertainFaultGeometry, yes]
-
A.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
B.
hasUncertainBoundary
Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
-
C.
hasUncertainParameters
Indicates that the relationship or action involves parameters whose values, conditions, or characteristics are not fully known, fixed, or reliably determined.
-
D.
hasUncertainOuterBoundary
Indicates that the outer boundary of an entity is not precisely defined, fixed, or clearly determined.
-
E.
hasUncertainDistance
Indicates that the distance between two entities is not known precisely or cannot be determined with certainty.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 8:56 a.m.