Triple
T15757593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innerste |
E382006
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Lamme |
E379325
|
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: Lamme | Statement: [Innerste, hasTributary, Lamme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lamme Context triple: [Innerste, hasTributary, Lamme]
-
A.
Lamme
chosen
Lamme is a small river in Lower Saxony, Germany, that serves as a tributary of the Innerste.
-
B.
Lamme
Lamme was an influential figure in electrical engineering whose legacy is honored by the AIEE Lamme Medal.
-
C.
Hemulen
Hemulen is a character from Tove Jansson’s Moomin series, typically portrayed as a tall, earnest, and somewhat pedantic creature obsessed with hobbies like stamp collecting and botany.
-
D.
Lahmu
Lahmu is a protective Mesopotamian deity or mythological figure, often depicted as a bearded man with a red sash and associated with primordial waters and temple guardianship.
-
E.
Lomme
Lomme is a suburban district and former commune that now forms part of the metropolitan area of Lille in northern France.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff877311dc8190b55fe7ca5c0843da |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 4:47 a.m.