Triple
T5251513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isar |
E118598
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Amper |
E206210
|
NE 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: Amper | Statement: [Isar, hasTributary, Amper]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amper Context triple: [Isar, hasTributary, Amper]
-
A.
Amper
chosen
The Amper is a river in Bavaria, Germany, known for flowing from the Ammersee toward the Isar and ultimately contributing to the Danube river system.
-
B.
ampere
The ampere is the SI base unit of electric current, defining the amount of electric charge passing a point in a circuit per unit time.
-
C.
Ohm
The Ohm is a river in the German state of Hesse that flows through towns such as Marburg before joining the Lahn.
-
D.
Anput
Anput is an ancient Egyptian goddess associated with funerary rites and protection, often depicted as a female counterpart to the jackal-headed god Anubis.
-
E.
Ampère (unit of electric current)
The ampere is the International System of Units (SI) base unit that quantifies electric current.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe7005308190a659efbd779c314b |
completed | March 21, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:50 p.m.