Triple
T5138584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piekar |
E115888
|
entity |
| Predicate | hasVariant |
P455
|
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: [Piekar, hasVariant, Pekar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pekar Context triple: [Piekar, hasVariant, 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.
Peki'in
Peki'in is an ancient village in northern Israel known for its continuous Jewish presence over centuries and its historical, religious, and archaeological significance.
-
D.
Pecile
Pecile is a large colonnaded garden and pool complex within Hadrian’s Villa at Tivoli, designed as a central courtyard for leisure, reflection, and display of imperial grandeur.
-
E.
Pegu
Pegu is an important historical city in Lower Myanmar that once served as the political and cultural center of the Mon people and a major hub of regional trade and Buddhism.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd787acd18819087f09db885893c3e |
completed | March 20, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec4d342c8819088f67c01d3769a6d |
completed | March 21, 2026, 4:18 p.m. |
Created at: March 20, 2026, 1:43 p.m.