Triple
T6911654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Census-designated place |
E159947
|
entity |
| Predicate | mayChangeBetween |
P8775
|
FINISHED |
| Object | census cycles |
—
|
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: census cycles | Statement: [Census-designated place, mayChangeBetween, census cycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayChangeBetween Context triple: [Census-designated place, mayChangeBetween, census cycles]
-
A.
canBeModifiedBetween
chosen
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
B.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
C.
mayAmend
Indicates that one party has the authority or permission to modify, revise, or change something that already exists.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c135b48190b332aedf1d52bdb7 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.