Triple
T29699954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qādir of Toledo |
E751453
|
entity |
| Predicate | politicalStatusInValencia |
P190489
|
FINISHED |
| Object | client ruler |
—
|
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: client ruler | Statement: [al-Qādir of Toledo, politicalStatusInValencia, client ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusInValencia Context triple: [al-Qādir of Toledo, politicalStatusInValencia, client ruler]
-
A.
populationRankInValencianCommunity
Indicates the relative position of an entity in terms of population size compared to other entities within the Valencian Community.
-
B.
statusInSpain
Indicates the legal, social, or official condition or standing that an entity has within the jurisdiction of Spain.
-
C.
capitalAsRulerOfValencia
Indicates that an entity serves as the capital city in its role as the ruling or administrative center of Valencia.
-
D.
officialNameInValencian
Indicates the officially recognized name of an entity when expressed in the Valencian language.
-
E.
legalStatusWithinCastile
Indicates the legal standing or rights an entity holds under the laws and jurisdiction specific to Castile.
- F. None of above. chosen
Provenance (4 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_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 28, 2026, 7:23 p.m.