Triple
T27835756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エポスカード |
E703221
|
entity |
| Predicate | ブランド前身 |
P1501
|
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.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
brandFounded
Indicates that a specific brand was established or created at a particular point in time or by a particular founder or entity.
-
C.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
-
D.
brandMergedWith
Indicates that two previously distinct brands have combined into a single unified brand entity, typically through merger or acquisition.
-
E.
brandEvolution
Indicates how a brand’s identity, positioning, or attributes change and develop over time.
- 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.