Triple
T35249473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łęczyca castellany |
E1018055
|
entity |
| Predicate | appliesToTypeOfArea |
P6822
|
FINISHED |
| Object | district around a royal stronghold |
—
|
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: district around a royal stronghold | Statement: [Łęczyca castellany, appliesToTypeOfArea, district around a royal stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTypeOfArea Context triple: [Łęczyca castellany, appliesToTypeOfArea, district around a royal stronghold]
-
A.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
B.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
C.
isTypeOfAreaWithin
Indicates that one area is a specific type or category of area that exists within another, larger area.
-
D.
appliesToUrbanAreaType
Indicates that something (such as a rule, measure, or classification) is applicable specifically to a particular type or category of urban area.
-
E.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
- 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_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.