Triple
T31458398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR |
E802517
|
entity |
| Predicate | denotesCountryWithHistoricalRegion |
P138136
|
FINISHED |
| Object | Persia |
—
|
NE NERFINISHED |
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: Persia | Statement: [IR, denotesCountryWithHistoricalRegion, Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesCountryWithHistoricalRegion Context triple: [IR, denotesCountryWithHistoricalRegion, Persia]
-
A.
historicalRegionNowInCountry
Indicates that a historical region is currently located within the borders or jurisdiction of a specified modern country.
-
B.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
C.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
D.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
E.
historicallyAssociatedWithModernCountry
chosen
Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
- F. None of above.
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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 9:18 p.m.