Triple
T32784826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California (1853–1854) |
E838464
|
entity |
| Predicate | capitalMoveFromBeniciaYear |
P14816
|
FINISHED |
| Object | 1854 |
—
|
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: 1854 | Statement: [California (1853–1854), capitalMoveFromBeniciaYear, 1854]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalMoveFromBeniciaYear Context triple: [California (1853–1854), capitalMoveFromBeniciaYear, 1854]
-
A.
historicalFunctionTransferredInYear
Indicates that a historical function, role, or responsibility was transferred from one entity to another in a specified year.
-
B.
capitalMovedFrom
Indicates that a capital city was relocated from one place (the source) to another (the destination).
-
C.
capitalFromYear
Indicates that a location serves as the capital of a political or administrative entity starting from a specified year.
-
D.
movedToInYear
Indicates that an entity changed location or residence to a specified place in a particular year.
-
E.
dateCapitalMoved
chosen
Indicates the date on which a capital city was officially relocated from one place 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:14 a.m.