Triple
T11259810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment Projections |
E266530
|
entity |
| Predicate | typicalBaseYear |
P68415
|
FINISHED |
| Object | most recent completed calendar 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: most recent completed calendar year | Statement: [Employment Projections, typicalBaseYear, most recent completed calendar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaseYear Context triple: [Employment Projections, typicalBaseYear, most recent completed calendar year]
-
A.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
B.
typicalStartYear
Indicates the year in which something (such as an event, activity, or process) usually or customarily begins.
-
C.
yearOfReference
chosen
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
D.
firstPermanentBaseYear
Indicates the year in which an entity’s first permanent base or facility was initially established.
-
E.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.