Triple
T3879539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Empire |
E92786
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | perper |
E296628
|
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: perper | Statement: [Serbian Empire, currency, perper]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: perper Context triple: [Serbian Empire, currency, perper]
-
A.
Per
Per is a Scandinavian masculine given name, commonly used in Norway, Sweden, and Denmark as a form of Peter.
-
B.
Pe
Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
-
C.
perpera
chosen
The perpera was a medieval Bulgarian coin and monetary unit used during the Second Bulgarian Empire.
-
D.
PAR
PAR is the IATA city code representing the collective airport system serving Paris, France, including major airports such as Charles de Gaulle and Orly.
-
E.
Perur
Perur is a historic locality near Coimbatore in Tamil Nadu, India, known for its ancient temples and cultural significance.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec7438808190b6c90fcb3000ebe9 |
completed | March 9, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51253da2081908689f06975fb4db1 |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.