Triple
T12244831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henryk Sucharski |
E291824
|
entity |
| Predicate | placeOfDeath |
P21
|
FINISHED |
| Object | Neapol |
E14805
|
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: Neapol | Statement: [Henryk Sucharski, placeOfDeath, Neapol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neapol Context triple: [Henryk Sucharski, placeOfDeath, Neapol]
-
A.
Neapoli
Neapoli is a small town in eastern Crete, Greece, known for its traditional architecture and role as a local administrative and cultural center.
-
B.
Nápoles
Nápoles is a middle- to upper-class residential and commercial neighborhood in Mexico City, known for its modern architecture, the World Trade Center complex, and a mix of offices, restaurants, and apartment buildings.
-
C.
Naples
chosen
Naples is a historic coastal city in southern Italy renowned for its rich cultural heritage, vibrant street life, and as the birthplace of pizza.
-
D.
Naples
Naples is a coastal city in southwest Florida known for its upscale shopping, golf courses, and Gulf of Mexico beaches.
-
E.
Naples
Naples is the first-generation AMD EPYC server processor family based on the Zen microarchitecture, designed for high-core-count, data center, and enterprise workloads.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb724448190be29fc1d2b946ab7 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62a9057408190a25f44d773b2b178 |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:51 p.m.