Triple
T5999984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Plan |
E133568
|
entity |
| Predicate | scheduledFinalPaymentYear |
P18640
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Young Plan, scheduledFinalPaymentYear, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledFinalPaymentYear Context triple: [Young Plan, scheduledFinalPaymentYear, 1988]
-
A.
debtFullyRepaidYear
chosen
Indicates the specific year in which a debt obligation has been completely repaid.
-
B.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
C.
postponedToYear
Indicates that an event or action has been delayed and rescheduled to occur in the specified calendar year.
-
D.
isFinalInstallmentOf
Indicates that one work or item is the concluding or last part in a series, sequence, or collection of related works.
-
E.
commissionYear
Indicates the year in which something (such as a work, project, or asset) was formally commissioned or authorized to be created or undertaken.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee5e7bc8190aaa87605fa7b102e |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.