Triple
T21234829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 磯崎 新 |
E523314
|
entity |
| Predicate | 著名な分野での評価 |
P39276
|
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.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
B.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
C.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
D.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
E.
hasNotableRecognitionAs
Indicates that an entity has received notable recognition, distinction, or status specifically in the role, capacity, or identity denoted by the related 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7351f0e988190bb77b598cb8a9532 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.