Triple
T31545451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luristan |
E804859
|
entity |
| Predicate | capitalInQajarEra |
P134108
|
FINISHED |
| Object | Khorramabad |
—
|
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: Khorramabad | Statement: [Luristan, capitalInQajarEra, Khorramabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalInQajarEra Context triple: [Luristan, capitalInQajarEra, Khorramabad]
-
A.
caliphateCapital
Indicates that one entity serves as the capital city or administrative center of a particular caliphate.
-
B.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
C.
capitalOfCountryRuled
Indicates that a city serves as the capital of a country that is (or was) governed by a specified ruler or ruling entity.
-
D.
capitalOfHistoricalRule
Indicates that one place served as the capital city or seat of government for another entity during a specific historical period of its rule.
-
E.
capitalCityDuringEra
chosen
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 30, 2026, 10:08 p.m.