Triple
T3907380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niko Pirosmani |
E87233
|
entity |
| Predicate | recognizedPosthumously |
P5766
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Niko Pirosmani, recognizedPosthumously, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedPosthumously Context triple: [Niko Pirosmani, recognizedPosthumously, true]
-
A.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
isPosthumousWorkOf
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
C.
canBeAwardedPosthumously
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
-
D.
isPosthumousAwardRecipientOf
Indicates that an entity received an award that was granted after their death.
-
E.
posthumousReputation
chosen
Indicates the reputation or standing attributed to a person after their death.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.