Triple
T24228129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ležáky |
E601650
|
entity |
| Predicate | originalEconomicActivity |
P19843
|
FINISHED |
| Object | stone quarrying |
—
|
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: stone quarrying | Statement: [Ležáky, originalEconomicActivity, stone quarrying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEconomicActivity Context triple: [Ležáky, originalEconomicActivity, stone quarrying]
-
A.
formerEconomicActivity
chosen
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
B.
hasEconomicActivity
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
C.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
-
D.
hasEconomicActivityLevel
Indicates the degree or intensity of economic activity associated with an entity, such as its level of production, trade, or financial transactions.
-
E.
primarySectorActivity
Indicates the main industry or sector in which an entity primarily conducts its activities or operations.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e11e188190bd257f24cb593039 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.