Triple
T8002823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoyarsk |
E186291
|
entity |
| Predicate | isMajorIndustrialCenter |
P3436
|
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: [Krasnoyarsk, isMajorIndustrialCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorIndustrialCenter Context triple: [Krasnoyarsk, isMajorIndustrialCenter, true]
-
A.
isIndustrialCenter
chosen
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
B.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
C.
isMajorIndustrialEconomy
Indicates that an entity is one of the world’s leading industrialized economies, characterized by large-scale industrial output and significant influence in global economic activity.
-
D.
isEconomicCenter
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
E.
hasMajorCommercialCentre
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf2918081909ee0afab11caed63 |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.