Triple

T32731390
Position Surface form Disambiguated ID Type / Status
Subject Transverse Ranges fault system E836963 entity
Predicate includes P1393 FINISHED
Object Red Mountain Fault
The Red Mountain Fault is a significant geological fault in Southern California that forms part of the complex, earthquake-prone Transverse Ranges region.
E2033558 NE 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: Red Mountain Fault | Statement: [Transverse Ranges fault system, includes, Red Mountain Fault]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Red Mountain Fault
Triple: [Transverse Ranges fault system, includes, Red Mountain Fault]
Generated description
The Red Mountain Fault is a significant geological fault in Southern California that forms part of the complex, earthquake-prone Transverse Ranges region.

Provenance (5 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_69f34935fb048190ad4967420581f835 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c8cd5cd48190b4d44faed8fcce07 completed May 3, 2026, 4:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34e4f1ffc4819090c87876d1a5abf2 completed June 19, 2026, 6:42 a.m.
NEDg Description generation batch_6a34e5b49a648190aca8b4ea64bb77da completed June 19, 2026, 6:46 a.m.
NED2 Entity disambiguation (via description) batch_6a34e66fc7fc81908758e4f67ce150b4 completed June 19, 2026, 6:49 a.m.
Created at: May 1, 2026, 1:11 a.m.