Triple
T1605591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security wage base limit |
E34495
|
entity |
| Predicate | timeIndexed |
P30229
|
FINISHED |
| Object | varies by tax year |
—
|
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: varies by tax year | Statement: [Social Security wage base limit, timeIndexed, varies by tax year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIndexed Context triple: [Social Security wage base limit, timeIndexed, varies by tax year]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timeCoordinateType
Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
E.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
- F. None of above. chosen
Provenance (4 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93fa5aa04819084d1154ef900303f |
completed | March 5, 2026, 8:32 a.m. |
Created at: March 4, 2026, 7:28 p.m.