Triple

T30444743
Position Surface form Disambiguated ID Type / Status
Subject Santa Ana winds E774545 entity
Predicate alsoKnownAs P39 FINISHED
Object Santana winds
Santana winds are strong, dry, and often hot seasonal winds that blow from inland deserts toward the Southern California coast, frequently elevating wildfire risk.
E1915685 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: Santana winds | Statement: [Santa Ana winds, alsoKnownAs, Santana winds]
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: Santana winds
Triple: [Santa Ana winds, alsoKnownAs, Santana winds]
Generated description
Santana winds are strong, dry, and often hot seasonal winds that blow from inland deserts toward the Southern California coast, frequently elevating wildfire risk.

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_69f22493ef9c8190ae8c2afcb7f994c8 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f686be108c8190a8ec98dc286ab03b completed May 2, 2026, 11:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2798c3bfd08190920588e34d2ebdbe completed June 9, 2026, 4:38 a.m.
NEDg Description generation batch_6a279d2bfafc8190a9dca1bb15c6602d completed June 9, 2026, 4:57 a.m.
NED2 Entity disambiguation (via description) batch_6a279d8d99fc8190a3a9805b65f4a1e2 completed June 9, 2026, 4:58 a.m.
Created at: April 29, 2026, 8:08 p.m.