Triple
T22324173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blachernae Palace |
E551860
|
entity |
| Predicate | becamePrimaryResidenceIn |
P24903
|
FINISHED |
| Object | 11th century |
—
|
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: 11th century | Statement: [Blachernae Palace, becamePrimaryResidenceIn, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becamePrimaryResidenceIn Context triple: [Blachernae Palace, becamePrimaryResidenceIn, 11th century]
-
A.
usedAsOfficialResidenceSince
chosen
Indicates that an entity has served as the formally designated official residence of another entity starting from a specified point in time.
-
B.
succeededByResidence
Indicates that one residence directly follows and replaces another as the primary place of dwelling for an entity.
-
C.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
D.
usedAtResidence
Indicates that an object, resource, or service is utilized within or for the purposes of a particular residence.
-
E.
laterResidenceShiftOf
Indicates that one residence shift event occurs chronologically after another residence shift event for the same entity.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576668b48190a78848c4a54acb39 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.