Triple
T33085740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loma Prieta |
E846633
|
entity |
| Predicate | typicalReferentType |
P206344
|
FINISHED |
| Object | natural elevation |
—
|
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: natural elevation | Statement: [Loma Prieta, typicalReferentType, natural elevation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReferentType Context triple: [Loma Prieta, typicalReferentType, natural elevation]
-
A.
typicalTargetType
Indicates the usual or most common type or category of entity that serves as the target or recipient in a given relationship or action.
-
B.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
C.
typicalConstituentType
Indicates the usual or characteristic type of component that typically makes up or forms part of something.
-
D.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:26 a.m.