Triple
T28441247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammadid dynasty |
E715715
|
entity |
| Predicate | capitalRelocationDate |
P14816
|
FINISHED |
| Object | late 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: late 11th century | Statement: [Hammadid dynasty, capitalRelocationDate, late 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRelocationDate Context triple: [Hammadid dynasty, capitalRelocationDate, late 11th century]
-
A.
dateCapitalMoved
chosen
Indicates the date on which a capital city was officially relocated from one place to another.
-
B.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
C.
capitalMovedFrom
Indicates that a capital city was relocated from one place (the source) to another (the destination).
-
D.
relocatedCompanyHeadquartersTo
Indicates that a company moved its main headquarters from a previous location to a new specified location.
-
E.
administrativeCenterMovedFrom
Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 1:46 a.m.