Triple
T30685440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korosten |
E781171
|
entity |
| Predicate | wasFortifiedSettlementOf |
P25570
|
FINISHED |
| Object | Drevlians |
—
|
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: Drevlians | Statement: [Korosten, wasFortifiedSettlementOf, Drevlians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFortifiedSettlementOf Context triple: [Korosten, wasFortifiedSettlementOf, Drevlians]
-
A.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
B.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
C.
wasCitadelOf
chosen
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
D.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
E.
fortificationTypeBesieged
Indicates that a specific type of fortification is the target of a siege or besieging action.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b83da3881908f819b08aaba4ff2 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:33 p.m.