Triple
T19529888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长白山 |
E488628
|
entity |
| Predicate | 水系源头 |
P25636
|
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.
sourceOfWatercourse
chosen
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
B.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
C.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
D.
formsHeadwatersWith
Indicates that two or more watercourses join or originate together to create the initial source or headwaters of a larger river or stream.
-
E.
waterOrigin
Indicates the source or starting location from which the water originates or is supplied.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363dfd6c8190aaa0b374184965bb |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.