Triple
T23518982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKS |
E574448
|
entity |
| Predicate | issuerHasBusinessModel |
P74458
|
FINISHED |
| Object | multinational retailer |
—
|
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: multinational retailer | Statement: [MKS, issuerHasBusinessModel, multinational retailer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerHasBusinessModel Context triple: [MKS, issuerHasBusinessModel, multinational retailer]
-
A.
usesBusinessModel
Indicates that one entity operates according to, or applies in practice, the business model defined or provided by another entity.
-
B.
hasBusinessModelCharacteristic
Indicates that a business model possesses or exhibits a specific feature, quality, or attribute.
-
C.
issuerBusinessType
Indicates the category or nature of business activity that the issuing entity is engaged in.
-
D.
businessModelType
chosen
Indicates the type or category of business model that characterizes how an entity creates, delivers, and captures value.
-
E.
businessModelElement
Indicates that one entity functions as a component or element within the overall business model of another entity.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa84fe7c8190aa1078a118af7d61 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.