Triple
T17079791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvey Pekar |
E414440
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pekar |
E118666
|
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: Pekar | Statement: [Harvey Pekar, familyName, Pekar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pekar Context triple: [Harvey Pekar, familyName, Pekar]
-
A.
Pekar
chosen
Pekar is a surname of Central or Eastern European origin, notably associated with several cultural and artistic figures.
-
B.
Pekat
Pekat is a settlement on the Indonesian island of Sumbawa that was devastated by the catastrophic 1815 eruption of Mount Tambora.
-
C.
Peketa
Peketa is a small coastal settlement in New Zealand’s South Island, located just south of the town of Kaikōura.
-
D.
Pakir
Pakir is a given name most notably associated with Avul Pakir Jainulabdeen Abdul Kalam, the former President of India and renowned aerospace scientist.
-
E.
Peca
Peca is the surname of Michael Peca, a former professional ice hockey player and two-time Selke Trophy–winning center in the NHL.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe24a6481908b4596c95220df4a |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ee243c081909aa6d470e002222a |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.