Triple
T30789951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subh of Córdoba |
E784064
|
entity |
| Predicate | endOfRegency |
P52345
|
FINISHED |
| Object | late 980s |
—
|
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 980s | Statement: [Subh of Córdoba, endOfRegency, late 980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfRegency Context triple: [Subh of Córdoba, endOfRegency, late 980s]
-
A.
regencyEnded
Indicates that a period during which one party governed on behalf of another (a regency) has come to an end.
-
B.
regencyEndApprox
chosen
Indicates that the end of a regency period is known only approximately rather than as an exact date.
-
C.
regencyEndYear
Indicates the calendar year in which a regency—rule exercised on behalf of another, typically a monarch—comes to an end.
-
D.
includesRegency
Indicates that one entity’s scope, period, or authority encompasses or contains a regency associated with another entity.
-
E.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:41 p.m.