Triple
T5687690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Persian |
E125351
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Pars |
E128420
|
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: Pars | Statement: [Middle Persian, region, Pars]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pars Context triple: [Middle Persian, region, Pars]
-
A.
Pars
chosen
Pars is the ancient name for the region and people of Persia, from which the term "Persian" is derived.
-
B.
The Pars
The Pars is the commonly used nickname for Dunfermline Athletic Football Club, a Scottish professional football team based in Dunfermline, Fife.
-
C.
Parl
Parl is the commonly used abbreviation for the Parliament of Singapore, the country's unicameral legislative body.
-
D.
Parsa
Parsa is the ancient name of the Persian people and their homeland, from which the ethnonym "Persian" is historically derived.
-
E.
Parap
Parap is an inner-city suburb of Darwin in Australia's Northern Territory, known for its popular weekend markets and tropical, laid-back atmosphere.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c023be18a081908c72fb5b0e1852f9 |
completed | March 22, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a43cce88190b8ac801018f05561 |
completed | March 22, 2026, 9:08 p.m. |
Created at: March 22, 2026, 3:44 p.m.