Triple
T23285293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 泰州 |
E588968
|
entity |
| Predicate | 著名河流 |
P57854
|
FINISHED |
| Object | 京杭大运河 |
—
|
LITERAL 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: 京杭大运河 | Statement: [泰州, 著名河流, 京杭大运河]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 著名河流 Context triple: [泰州, 著名河流, 京杭大运河]
-
A.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
B.
majorRiverRole
Indicates that a river plays a primary or dominant role in a specified context, such as geography, economy, culture, or ecology, relative to other rivers in the area.
-
C.
hasLongestRiver
Indicates that one entity possesses or contains the river that is longer than any other river associated with the compared entities.
-
D.
isOneOfLargestRiversIn
Indicates that a river is among the largest rivers within a specified geographic region or area.
-
E.
isMajorWatercourseOf
chosen
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
- F. None of above.
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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964600888190b40ecbefdc8aec64 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:59 p.m.