Triple
T27178456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverdlovsk-45 |
E683118
|
entity |
| Predicate | mainEmployer |
P129978
|
FINISHED |
| Object | Ural Electrochemical Combine |
—
|
NE NERFINISHED |
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: Ural Electrochemical Combine | Statement: [Sverdlovsk-45, mainEmployer, Ural Electrochemical Combine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEmployer Context triple: [Sverdlovsk-45, mainEmployer, Ural Electrochemical Combine]
-
A.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
B.
parentEmployer
Indicates that one organization is the direct or higher-level employer of another organization or entity.
-
C.
formerEmployer
Indicates that one entity previously employed the other but no longer does so.
-
D.
employerOrPrimaryClient
chosen
Indicates that one entity serves as the main employer or principal client of another entity in a work or service relationship.
-
E.
employerService
Indicates that one entity provides employment-related services or functions to another entity, typically in the role of an employer.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257c0d58819081803213a42252b2 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:27 a.m.