Triple
T35249441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łęczyca Land |
E1018054
|
entity |
| Predicate | hadMedievalStronghold |
P1090
|
FINISHED |
| Object | Łęczyca 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: Łęczyca stronghold | Statement: [Łęczyca Land, hadMedievalStronghold, Łęczyca stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMedievalStronghold Context triple: [Łęczyca Land, hadMedievalStronghold, Łęczyca stronghold]
-
A.
historicalStronghold
chosen
Indicates that a location has historically served as a fortified center of power, defense, or control for a group or authority.
-
B.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
C.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
-
D.
traditionalPartyStronghold
Indicates that a particular area or region has historically and consistently provided strong electoral support for a traditional or long-established political party.
-
E.
hasMedievalBuilding
Indicates that one entity possesses, contains, or includes a building dating from the medieval 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.