Triple
T21280080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Pieck |
E524496
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pieck |
—
|
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: Pieck | Statement: [Arthur Pieck, familyName, Pieck]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pieck Context triple: [Arthur Pieck, familyName, Pieck]
-
A.
Pieck
chosen
Pieck is a German surname most notably associated with Wilhelm Pieck, the first and only president of the German Democratic Republic (East Germany).
-
B.
Piekar
Piekar is a surname or variant form derived from the occupational term "baker," commonly found in Central or Eastern European languages.
-
C.
Piikani
Piikani are an Indigenous people of the Blackfoot Confederacy traditionally based in the northern Great Plains of North America.
-
D.
Pecka
Pecka is a small settlement located within the municipality of Osečina in western Serbia.
-
E.
Piecki
Piecki is a village in northern Poland located in the Warmian-Masurian Voivodeship, known for its proximity to the region’s lakes and forests.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73659b56c8190af283348378b1cff |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:02 p.m.