Triple
T21571439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Tientsin (1885) |
E532292
|
entity |
| Predicate | signedIn |
P441
|
FINISHED |
| Object | Tianjin |
—
|
NE NERFINISHED |
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: Tianjin | Statement: [Treaty of Tientsin (1885), signedIn, Tianjin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tianjin Context triple: [Treaty of Tientsin (1885), signedIn, Tianjin]
-
A.
Tianjin
chosen
Tianjin is a major port city and industrial hub in northern China, located near Beijing along the Bohai Sea.
-
B.
Tân An
Tân An is a city in southern Vietnam that serves as an administrative, economic, and cultural hub in the Mekong Delta region.
-
C.
Tiāntán
Tiāntán is the Chinese pinyin name for the Temple of Heaven, a historic imperial religious complex in Beijing where Ming and Qing dynasty emperors performed annual ceremonies to pray for good harvests.
-
D.
Toishan
Toishan is an older English romanization of Taishan, a county-level city in Guangdong, China, historically known for its large overseas Chinese diaspora.
-
E.
Beijing
Beijing is the capital city of China, a major political, cultural, and economic center known for its rich history and rapid modern development.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cd50188190b44eb25fb87312bb |
completed | April 27, 2026, 4:45 a.m. |
Created at: April 16, 2026, 6:30 p.m.