Triple
T26585359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polans |
E667193
|
entity |
| Predicate | fortifiedSettlements |
P81783
|
FINISHED |
| Object | Poznań stronghold |
—
|
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: Poznań stronghold | Statement: [Polans, fortifiedSettlements, Poznań stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortifiedSettlements Context triple: [Polans, fortifiedSettlements, Poznań stronghold]
-
A.
fortifiedSite
chosen
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
B.
fortificationTypeBesieged
Indicates that a specific type of fortification is the target of a siege or besieging action.
-
C.
fortificationsLaterControlledBy
Indicates that control over certain fortifications passed to a different entity at a later time.
-
D.
fortificationTypeDefended
Indicates the specific type of fortification that an entity is responsible for defending or protecting.
-
E.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e47cdc81909786f92cc0d5965f |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:05 a.m.