Triple
T22533417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東京都港区 |
E557098
|
entity |
| Predicate | containsCorporateHeadquarters |
P10544
|
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: [東京都港区, containsCorporateHeadquarters, ソニーグループ本社]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCorporateHeadquarters Context triple: [東京都港区, containsCorporateHeadquarters, ソニーグループ本社]
-
A.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
B.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
-
C.
hasParentCompanyHeadquarters
Indicates that a company’s parent organization has its main headquarters located at a specified place.
-
D.
hasHeadquartersFunctionFor
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
-
E.
employerHeadquarters
chosen
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.