Triple
T22185056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partie de campagne |
E548271
|
entity |
| Predicate | posthumousCompletionStatus |
P4225
|
FINISHED |
| Object | released unfinished |
—
|
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: released unfinished | Statement: [Partie de campagne, posthumousCompletionStatus, released unfinished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousCompletionStatus Context triple: [Partie de campagne, posthumousCompletionStatus, released unfinished]
-
A.
posthumousLegalStatus
Indicates the legal condition or recognition assigned to a person or entity after their death.
-
B.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
E.
posthumousAction
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa823888190829368de6db4aa91 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.