Triple
T8341568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberweser |
E195927
|
entity |
| Predicate | nameAppliesTo |
P82190
|
FINISHED |
| Object | upper course of the Weser River |
—
|
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: upper course of the Weser River | Statement: [Oberweser, nameAppliesTo, upper course of the Weser River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameAppliesTo Context triple: [Oberweser, nameAppliesTo, upper course of the Weser River]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
C.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
D.
namedTo
Indicates that one entity has been given or assigned a specific name referring to another entity.
-
E.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
- F. None of above. chosen
Provenance (4 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe9efec81908e0c9ded3963bac5 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:58 p.m.