Triple
T29699937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qādir of Toledo |
E751453
|
entity |
| Predicate | predecessorInToledo |
P97
|
FINISHED |
| Object | al-Maʾmūn of Toledo |
—
|
NE NERFINISHED |
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: al-Maʾmūn of Toledo | Statement: [al-Qādir of Toledo, predecessorInToledo, al-Maʾmūn of Toledo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInToledo Context triple: [al-Qādir of Toledo, predecessorInToledo, al-Maʾmūn of Toledo]
-
A.
predecessorInMyth
Indicates that one mythological figure, story, or element chronologically or narratively comes before and influences or sets the stage for another within a mythic tradition.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorAsBishopOfUrgell
Indicates that one individual previously held the position of Bishop of Urgell immediately before another individual.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorRealName
Indicates that one entity is the real (actual) name of the predecessor of 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:23 p.m.