Triple
T29266956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegerland |
E742000
|
entity |
| Predicate | primaryRiverSystem |
P36808
|
FINISHED |
| Object | Rhine basin |
—
|
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: Rhine basin | Statement: [Siegerland, primaryRiverSystem, Rhine basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRiverSystem Context triple: [Siegerland, primaryRiverSystem, Rhine basin]
-
A.
riverSystem
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.
primaryRiverRegion
Indicates that a given region is the main geographic area through which a particular river primarily flows or with which it is chiefly associated.
-
C.
hasMajorRiverSystem
chosen
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
D.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
E.
tributarySystemOf
Indicates that one political entity is subordinate to another, providing tribute or services in exchange for protection, recognition, or limited autonomy within a hierarchical system.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: April 28, 2026, 12:45 p.m.