Triple
T27835624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 株式会社丸井 |
E703217
|
entity |
| Predicate | 本社機能 |
P33384
|
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.
organizationalFunction
Indicates the role, purpose, or primary activity that an organization performs within a broader system or context.
-
B.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
C.
headquartersFunction
chosen
Indicates that an entity serves as the main administrative or central operating location (headquarters) for another entity.
-
D.
supportFunction
Indicates that one entity provides assistance, resources, or functionality that enables or enhances the operation or effectiveness of another entity.
-
E.
hasBackOfficeFunctionsIn
Indicates that an entity’s back-office operations or support functions are performed or located in a specified place or organizational unit.
- 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.