Triple
T14669473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles IV of Spain |
E344469
|
entity |
| Predicate | nobleAction |
P59544
|
FINISHED |
| Object | created the title Duke of Alcudia |
—
|
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: created the title Duke of Alcudia | Statement: [Charles IV of Spain, nobleAction, created the title Duke of Alcudia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleAction Context triple: [Charles IV of Spain, nobleAction, created the title Duke of Alcudia]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
C.
virtuePromoted
Indicates that one entity actively encourages, supports, or increases the presence or practice of a particular virtue in another entity or context.
-
D.
evaluatesAsNoble
Indicates that an entity is judged or classified as having noble status or qualities.
-
E.
significantAction
chosen
Indicates that an action taken by an entity is of notable importance or consequence within a given context or process.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.