Triple
T20985187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1790 United States census |
E516873
|
entity |
| Predicate | frequencyEstablished |
P85
|
FINISHED |
| Object | every 10 years |
—
|
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: every 10 years | Statement: [1790 United States census, frequencyEstablished, every 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyEstablished Context triple: [1790 United States census, frequencyEstablished, every 10 years]
-
A.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
-
C.
frequencyDependsOn
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
-
D.
frequencyClass
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
E.
frequencyRelation
Indicates a relationship that specifies how often one event, action, or state occurs in relation to another.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe218748190a987b9f922d9be1b |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.