Triple
T9617666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Community Survey |
E232257
|
entity |
| Predicate | dataReleaseFrequency |
P1389
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [American Community Survey, dataReleaseFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataReleaseFrequency Context triple: [American Community Survey, dataReleaseFrequency, annual]
-
A.
dataAvailableFrom
Indicates that a specified source or provider offers access to certain data starting from a particular point or under certain conditions.
-
B.
dataPublication
Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
-
C.
publicationFrequency
chosen
Indicates how often a publication or content is issued, released, or made available over a given period.
-
D.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
E.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aaf3a088190a00a7750c25b6c42 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.