Triple
T27141028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKF |
E681815
|
entity |
| Predicate | operatesInCountriesApproximate |
P20059
|
FINISHED |
| Object | over 100 |
—
|
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: over 100 | Statement: [SKF, operatesInCountriesApproximate, over 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInCountriesApproximate Context triple: [SKF, operatesInCountriesApproximate, over 100]
-
A.
operatesInCountries
chosen
Indicates that an entity conducts its activities or business within the specified countries.
-
B.
operatesFacilityInCountry
Indicates that an entity runs or manages a facility that is located within a specified country.
-
C.
operatesInTerritoriesOutside
Indicates that an entity conducts activities or maintains operations in geographic areas beyond its primary or home territories.
-
D.
operatesBrandInRegion
Indicates that an entity manages or runs a specific brand within a particular geographic region.
-
E.
operatedByCountry
Indicates that an entity (such as an organization, facility, or service) is run, managed, or controlled by a specific country or its government.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 9:09 a.m.