Triple

T7893550
Position Surface form Disambiguated ID Type / Status
Subject LinkedIn headquarters E183293 entity
Predicate locatedNear P294 FINISHED
Object Mountain View E29698 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: Mountain View | Statement: [LinkedIn headquarters, locatedNear, Mountain View]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mountain View
Context triple: [LinkedIn headquarters, locatedNear, Mountain View]
  • A. Mountain View chosen
    Mountain View is a Silicon Valley city in Northern California best known as a major technology hub and the home of companies like Google.
  • B. Mountain View
    Mountain View is a small unincorporated community in Contra Costa County, California, located in the San Francisco Bay Area.
  • C. Mountain View
    Mountain View is a small rural village in southern Alberta, Canada, situated within Cardston County near the Rocky Mountains.
  • D. Sunnyvale
    Sunnyvale is a suburban town in the Dallas–Fort Worth metropolitan area known for its residential character and proximity to Dallas, Texas.
  • E. Sunnyvale
    Sunnyvale is a major Silicon Valley city in Northern California known for its high-tech industry presence and suburban residential communities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a008fb88190a039fec40483ab93 completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde6a2bdd08190897705615109dae0 completed April 2, 2026, 3:46 a.m.
Created at: March 30, 2026, 5:01 p.m.