Triple
T12658626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siedlce |
E302354
|
entity |
| Predicate | isRegionalEconomicHub |
P13740
|
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: [Siedlce, isRegionalEconomicHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalEconomicHub Context triple: [Siedlce, isRegionalEconomicHub, true]
-
A.
isEconomicCenter
chosen
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
B.
isMajorEconomicAreaFor
Indicates that a location or region serves as a primary center of significant economic activity for a specified entity or sector.
-
C.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
D.
hasMajorEconomicRegion
Indicates that an entity includes, is associated with, or is part of a primary or significant economic region within a larger economic or geographic context.
-
E.
isMajorRegionalCenter
Indicates that a location functions as a primary hub of economic, administrative, or cultural activity within a specific geographic region.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.