Triple
T6917855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongling |
E160108
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Yangtze River |
E13303
|
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: Yangtze River | Statement: [Tongling, river, Yangtze River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yangtze River Context triple: [Tongling, river, Yangtze River]
-
A.
Yangtze River
chosen
The Yangtze River is the longest river in Asia and a crucial waterway in China, supporting major cities, transportation, agriculture, and hydroelectric power.
-
B.
Yellow River
The Yellow River is a river in the U.S. state of Florida that flows through the western Panhandle before emptying into Escambia Bay near the Gulf of Mexico.
-
C.
Yellow River
The Yellow River is a tributary stream that feeds into Lough Allen, a lake in the River Shannon system in Ireland.
-
D.
Yellow River
The Yellow River is the second-longest river in China, historically known as the cradle of Chinese civilization and notorious for its devastating floods and heavy silt load.
-
E.
Mao River
Mao River is a waterway flowing through Shanghai's Qingpu District, contributing to the area's local river network and drainage system.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9e17ea08190b8c4142af8adfba0 |
completed | March 27, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7510e26148190a75e660cedf1274e |
completed | March 28, 2026, 3:54 a.m. |
Created at: March 27, 2026, 2:26 p.m.