Triple
T28225590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammudid dynasty |
E711575
|
entity |
| Predicate | lostControlOfCórdoba |
P76678
|
FINISHED |
| Object | 1020s |
—
|
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: 1020s | Statement: [Hammudid dynasty, lostControlOfCórdoba, 1020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostControlOfCórdoba Context triple: [Hammudid dynasty, lostControlOfCórdoba, 1020s]
-
A.
cededToCastile
Indicates that control, ownership, or sovereignty over something was transferred or surrendered to Castile.
-
B.
lostSovereignty
chosen
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
C.
controlledByAfterReconquista
Indicates that one entity came under the control or authority of another entity following the Reconquista.
-
D.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
E.
lostTerritoryBy
Indicates that one entity has had control or ownership of a territory taken away by another 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64383a09881908365b967641ab98f |
completed | May 2, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:49 p.m.