Triple
T6497324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constans II |
E148789
|
entity |
| Predicate | movedImperialResidenceYear |
P71214
|
FINISHED |
| Object | c. 663 |
—
|
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: c. 663 | Statement: [Constans II, movedImperialResidenceYear, c. 663]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedImperialResidenceYear Context triple: [Constans II, movedImperialResidenceYear, c. 663]
-
A.
movedImperialCapitalTo
Indicates that a ruler or governing authority relocated the primary seat of imperial government from one capital city to another.
-
B.
movedImperialCapitalFrom
Indicates the action of transferring an imperial capital city from one location to another.
-
C.
servedAsImperialResidenceFrom
Indicates that an entity functioned as an imperial residence starting from a specified point in time.
-
D.
usedAsRoyalResidenceUntil
Indicates that something served as a royal residence up to a specified point in time.
-
E.
yearsInUseAsImperialPalace
Indicates the number of years a place served as the official imperial palace.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
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:41 p.m.