Triple
T14889625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Argelander |
E359718
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Memel |
E117663
|
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: Memel | Statement: [Friedrich Argelander, placeOfBirth, Memel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Memel Context triple: [Friedrich Argelander, placeOfBirth, Memel]
-
A.
Memel
chosen
Memel is the former German name for the Baltic port city now known as Klaipėda in Lithuania.
-
B.
Memelland
Memelland was a historically contested region around the city of Memel (now Klaipėda, Lithuania), notable for its shifting control between Germany and Lithuania in the 20th century.
-
C.
Mēmele
Mēmele is a river in the Baltic region that serves as one of the headwaters forming Latvia’s Lielupe River.
-
D.
Pepe
Pepe is a Brazilian-born Portuguese central defender renowned for his aggressive, physical style of play and long, trophy-laden career with clubs like Real Madrid and the Portugal national team.
-
E.
Pepe
Pepe is a legendary Brazilian forward who starred for Santos FC and the Brazil national team in the 1950s and 1960s, renowned for his powerful left-footed shots and prolific goal-scoring.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b61407481908a618d14c56d2abf |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 2:09 a.m.