Triple
T34623839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Gurganj |
E889077
|
entity |
| Predicate | cityStatusBeforeSiege |
P73538
|
FINISHED |
| Object | major urban center of Khwarazm |
—
|
LITERAL 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: major urban center of Khwarazm | Statement: [Siege of Gurganj, cityStatusBeforeSiege, major urban center of Khwarazm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStatusBeforeSiege Context triple: [Siege of Gurganj, cityStatusBeforeSiege, major urban center of Khwarazm]
-
A.
cityStatusDuringSiege
Indicates the condition or status of a city specifically during the period in which it is under siege.
-
B.
statusOfCityBeforeBattle
chosen
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
C.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
-
D.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
E.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.