Triple
T21834129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊東豊雄 |
E539073
|
entity |
| Predicate | 存命状況 |
P53287
|
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.
mortalStatus
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
B.
hasSurvivalStatus
chosen
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
-
C.
legalStatusAtEndOfLife
Indicates the legal classification or condition that applies to an entity at the time of its termination, dissolution, or death.
-
D.
canDieIn
Indicates that one entity is capable of dying, ceasing to exist, or being destroyed within, because of, or in the context of another entity or situation.
-
E.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a5eeb88190b58b5b6d363cd6e3 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.