Triple
T27534916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adjusted Compensation Act of 1924 |
E695070
|
entity |
| Predicate | payoutDateScheduled |
P4691
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Adjusted Compensation Act of 1924, payoutDateScheduled, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payoutDateScheduled Context triple: [Adjusted Compensation Act of 1924, payoutDateScheduled, 1945]
-
A.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
B.
paysAfter
Indicates that one entity makes a payment to another entity only after a specified event, condition, or time has occurred.
-
C.
chargeDate
Indicates the date on which a financial charge or billing action is applied or recorded.
-
D.
datePlanned
chosen
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
E.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5996508190894a769a5199945d |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:28 p.m.