Triple
T33038328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadrinsk |
E845381
|
entity |
| Predicate | hasNotableEconomicRole |
P2223
|
FINISHED |
| Object | regional trade center |
—
|
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: regional trade center | Statement: [Shadrinsk, hasNotableEconomicRole, regional trade center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEconomicRole Context triple: [Shadrinsk, hasNotableEconomicRole, regional trade center]
-
A.
hasEconomicRole
chosen
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
B.
hasNotableImpact
Indicates that one entity exerts a significant or noteworthy influence or effect on another entity or context.
-
C.
hasNoMajorIndustry
Indicates that the referenced place or entity does not possess any dominant or significant industrial sector.
-
D.
hasEconomicInterest
Indicates that one entity stands to gain or lose financially or materially from the performance, decisions, or outcomes associated with another entity.
-
E.
hasEconomicPosition
Indicates that an entity holds a particular role, status, or standing within an economic system or structure.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: May 1, 2026, 1:24 a.m.