Triple
T23471397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Przysucha County |
E570137
|
entity |
| Predicate | hasSmallTownCenters |
P109384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Przysucha County, hasSmallTownCenters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSmallTownCenters Context triple: [Przysucha County, hasSmallTownCenters, true]
-
A.
hasCentralTownFeature
Indicates that a town possesses a specific central feature or focal element (such as a landmark, square, or facility) that characterizes its core area.
-
B.
hasSmallCommunities
chosen
Indicates that an entity possesses or is characterized by the presence of relatively small communities within it.
-
C.
hasSmallTownIndustry
Indicates that a small town possesses or supports a particular type of industry or industrial activity.
-
D.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
-
E.
isSmallCity
Indicates that a city has a relatively small population size or limited geographic/urban extent compared to typical cities.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a700bd0481908047aa4678217cbd |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:55 p.m.