Triple
T5161197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salo |
E116439
|
entity |
| Predicate | notableCompanyHistory |
P61859
|
FINISHED |
| Object | Nokia mobile phone factory |
—
|
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: Nokia mobile phone factory | Statement: [Salo, notableCompanyHistory, Nokia mobile phone factory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompanyHistory Context triple: [Salo, notableCompanyHistory, Nokia mobile phone factory]
-
A.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
-
B.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
C.
notableCommercial
Indicates that an entity is particularly well-known or significant in a commercial context, such as advertising, marketing, or business promotion.
-
D.
notableCompanyFoundedIn
Indicates that a company is recognized as notable and was founded in the specified location or time period.
-
E.
notableBusinessType
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of business.
- F. None of above. chosen
Provenance (4 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79073a54819080cd1e8de6fe906a |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:44 p.m.