Triple
T18520009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Paperwork Elimination Act |
E452558
|
entity |
| Predicate | implementationDeadline |
P8546
|
FINISHED |
| Object | 2003-10-21 |
—
|
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: 2003-10-21 | Statement: [Government Paperwork Elimination Act, implementationDeadline, 2003-10-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationDeadline Context triple: [Government Paperwork Elimination Act, implementationDeadline, 2003-10-21]
-
A.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
C.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
D.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
E.
facesDeadline
Indicates that an entity is approaching or subject to a specific due date or time limit by which a task or obligation must be completed.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338ce7e481908ee69ffe4f30d5a4 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.