Triple
T6531249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau places in Michigan |
E152234
|
entity |
| Predicate | updatedEvery |
P71451
|
FINISHED |
| Object | decennial census |
—
|
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: decennial census | Statement: [United States Census Bureau places in Michigan, updatedEvery, decennial census]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedEvery Context triple: [United States Census Bureau places in Michigan, updatedEvery, decennial census]
-
A.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
E.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbcf820819097ca33a5fc14fd64 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.