Triple
T19872414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 洛河 |
E477550
|
entity |
| Predicate | 河流类型 |
P1009
|
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.
riverSystem
chosen
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
B.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
C.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
D.
isRiverInHydrologicalSense
Indicates that a river, considered as a hydrological feature (its water flow and drainage characteristics), is located within or associated with a specified geographic or hydrological area.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d826f88190be04188997952d1b |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.