Triple

T36112493
Position Surface form Disambiguated ID Type / Status
Subject Simatai E1044535 entity
Predicate adjacentTo P224 FINISHED
Object Gubei Water Town
Gubei Water Town is a scenic resort-style ancient water town near the Simatai section of the Great Wall in Beijing, known for its traditional architecture, canals, and cultural tourism.
E2170674 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: Gubei Water Town | Statement: [Simatai, adjacentTo, Gubei Water Town]
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: Gubei Water Town
Triple: [Simatai, adjacentTo, Gubei Water Town]
Generated description
Gubei Water Town is a scenic resort-style ancient water town near the Simatai section of the Great Wall in Beijing, known for its traditional architecture, canals, and cultural tourism.

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_69f76e344a4c8190af3858c6d78ba88f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b2c94f348190b557683810cc573e completed May 3, 2026, 8:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38de0492ec81908bff20b21a6dcc1e completed June 22, 2026, 7:02 a.m.
NEDg Description generation batch_6a38debb5dec8190bf6b5faa18907623 completed June 22, 2026, 7:05 a.m.
NED2 Entity disambiguation (via description) batch_6a38e299db6481908dda9ad7c048f08e completed June 22, 2026, 7:22 a.m.
Created at: May 3, 2026, 4:08 p.m.