Triple
T37473880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau places in Alabama |
E931225
|
entity |
| Predicate | mayBeRevisedIn |
P12017
|
FINISHED |
| Object | intercensal geographic updates |
—
|
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: intercensal geographic updates | Statement: [United States Census Bureau places in Alabama, mayBeRevisedIn, intercensal geographic updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRevisedIn Context triple: [United States Census Bureau places in Alabama, mayBeRevisedIn, intercensal geographic updates]
-
A.
periodicallyRevisedAt
Indicates that something is updated or revised at recurring, regular points in time.
-
B.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
C.
mayBeModifiedBy
chosen
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
E.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.