Triple
T34115365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand of Castile, Lord of Ledesma |
E874955
|
entity |
| Predicate | lordshipOver |
P47636
|
FINISHED |
| Object | Ledesma |
—
|
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: Ledesma | Statement: [Ferdinand of Castile, Lord of Ledesma, lordshipOver, Ledesma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lordshipOver Context triple: [Ferdinand of Castile, Lord of Ledesma, lordshipOver, Ledesma]
-
A.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
B.
lordshipCreated
Indicates that a lordship was formally established or brought into existence.
-
C.
lordOf
chosen
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
D.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
E.
earldomHeldBy
Indicates that a specified earldom is or was held as a title by a particular person or 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb880008190bc1ca79d89580949 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.