Triple
T30789950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subh of Córdoba |
E784064
|
entity |
| Predicate | startOfRegency |
P73392
|
FINISHED |
| Object | 976 |
—
|
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: 976 | Statement: [Subh of Córdoba, startOfRegency, 976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfRegency Context triple: [Subh of Córdoba, startOfRegency, 976]
-
A.
regencyBegan
chosen
Indicates the point in time when a regency—rule exercised on behalf of another, typically a monarch—officially started.
-
B.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
C.
regencyStartApprox
Indicates that the beginning of a regency period is known only approximately rather than as an exact date.
-
D.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
regencyEndApprox
Indicates that the end of a regency period is known only approximately rather than as an exact date.
- 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_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 29, 2026, 8:41 p.m.