Triple

T27820702
Position Surface form Disambiguated ID Type / Status
Subject Walker & Eisen E702805 entity
Predicate designed P184 FINISHED
Object Hotel San Diego (San Diego)
Hotel San Diego was a historic early-20th-century hotel in downtown San Diego, California, known for its distinctive architecture and role in the city’s urban development.
E1793166 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: Hotel San Diego (San Diego) | Statement: [Walker & Eisen, designed, Hotel San Diego (San Diego)]
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: Hotel San Diego (San Diego)
Triple: [Walker & Eisen, designed, Hotel San Diego (San Diego)]
Generated description
Hotel San Diego was a historic early-20th-century hotel in downtown San Diego, California, known for its distinctive architecture and role in the city’s urban development.

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_69ef840ad1e88190b5bff2d1ddec8700 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6386e355481909572b6b36e501909 completed May 2, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a130343537c8190b33333d0a70ccccd completed May 24, 2026, 1:55 p.m.
NEDg Description generation batch_6a1303e852488190ad34cae264ed7752 completed May 24, 2026, 1:58 p.m.
NED2 Entity disambiguation (via description) batch_6a130498a5748190bf5560d2cc95f478 completed May 24, 2026, 2 p.m.
Created at: April 27, 2026, 5:48 p.m.