Triple

T29494
Position Surface form Disambiguated ID Type / Status
Subject 1906 San Francisco earthquake E588 entity
Predicate plateBoundary P944 FINISHED
Object boundary between Pacific Plate and North American Plate 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: boundary between Pacific Plate and North American Plate | Statement: [1906 San Francisco earthquake, plateBoundary, boundary between Pacific Plate and North American Plate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plateBoundary
Context triple: [1906 San Francisco earthquake, plateBoundary, boundary between Pacific Plate and North American Plate]
  • A. locatedOnTectonicBoundary chosen
    Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
  • B. borderedBy
    Indicates that one entity shares a common boundary or edge with another entity.
  • C. continent
    Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
  • D. oceanDrainageBasin
    Indicates the ocean into which a river system or drainage basin ultimately discharges its water.
  • E. hasCoastlineOn
    Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
  • F. None of above.

Provenance (3 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_69a2479dec388190967ba648663442c9 completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a2490019948190a89bb0910c60d462 completed Feb. 28, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69a2486d40348190b2d21fc444f499a6 completed Feb. 28, 2026, 1:44 a.m.
Created at: Feb. 28, 2026, 1:44 a.m.