Triple
T26968421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | 官邸所在地 |
P35922
|
FINISHED |
| Object | 東京都千代田区永田町2-3-1 |
—
|
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: 東京都千代田区永田町2-3-1 | Statement: [岸田文雄内閣, 官邸所在地, 東京都千代田区永田町2-3-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 官邸所在地 Context triple: [岸田文雄内閣, 官邸所在地, 東京都千代田区永田町2-3-1]
-
A.
formerOfficialResidence
Indicates that a location previously served as the official residence of a person or institution but no longer holds that status.
-
B.
aristocraticResidenceFor
Indicates that one entity serves as the residence or dwelling specifically designated for an aristocratic person or group.
-
C.
residenceAssociatedWithOffice
chosen
Indicates a relationship where a residence is connected or linked to a particular office, such as being located at, attached to, or officially designated for that office.
-
D.
officeHolderResidence
Indicates that a person holding an office resides or is officially based at a particular location or residence.
-
E.
houseSeat
Indicates that a particular location or structure serves as the primary residence or official dwelling place for an 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621233f2c81908c237f20c50c2ba3 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:37 a.m.