Triple
T14744340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau places in Oklahoma |
E346427
|
entity |
| Predicate | updatedDuring |
P71451
|
FINISHED |
| Object | each decennial census cycle |
—
|
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: each decennial census cycle | Statement: [United States Census Bureau places in Oklahoma, updatedDuring, each decennial census cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedDuring Context triple: [United States Census Bureau places in Oklahoma, updatedDuring, each decennial census cycle]
-
A.
modifiedDuring
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
updatedEvery
chosen
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
E.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d002708190a32a4a45e96fc389 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.