Triple
T32179101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employee Retention Credit |
E821933
|
entity |
| Predicate | coveredPeriod2020 |
P3058
|
FINISHED |
| Object | 2020-03-13 to 2020-12-31 |
—
|
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: 2020-03-13 to 2020-12-31 | Statement: [Employee Retention Credit, coveredPeriod2020, 2020-03-13 to 2020-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredPeriod2020 Context triple: [Employee Retention Credit, coveredPeriod2020, 2020-03-13 to 2020-12-31]
-
A.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
D.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
E.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:34 a.m.