Triple
T27835746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | マルイ |
E703220
|
entity |
| Predicate | ビジネスモデル |
P101504
|
FINISHED |
| Object | 小売とクレジットカード事業の連携 |
—
|
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: 小売とクレジットカード事業の連携 | Statement: [マルイ, ビジネスモデル, 小売とクレジットカード事業の連携]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ビジネスモデル Context triple: [マルイ, ビジネスモデル, 小売とクレジットカード事業の連携]
-
A.
businessModelType
Indicates the type or category of business model that characterizes how an entity creates, delivers, and captures value.
-
B.
businessModelElement
chosen
Indicates that one entity functions as a component or element within the overall business model of another entity.
-
C.
businessModelFocus
Indicates that one entity’s business model is centered on, tailored to, or primarily oriented around another entity or specific focus area.
-
D.
businessModelPioneerOf
Indicates that an entity was the first or among the first to introduce, develop, or popularize a particular business model that others later adopted.
-
E.
laterBusinessModel
Indicates that one business model occurs or is adopted after another in time, representing a subsequent or successor business model in a sequence.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:59 p.m.