Triple
T26567412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby House, London |
E666724
|
entity |
| Predicate | tenantNobleTitle |
P914
|
FINISHED |
| Object | 12th Earl of Derby |
—
|
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: 12th Earl of Derby | Statement: [Derby House, London, tenantNobleTitle, 12th Earl of Derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantNobleTitle Context triple: [Derby House, London, tenantNobleTitle, 12th Earl of Derby]
-
A.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
B.
associatedNobleTitle
chosen
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
D.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
E.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary title.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:56 a.m.