Triple
T28305458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Leila Primrose |
E713830
|
entity |
| Predicate | nobleTitleHeldThrough |
P165435
|
FINISHED |
| Object | Primrose family |
—
|
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: Primrose family | Statement: [Lady Leila Primrose, nobleTitleHeldThrough, Primrose family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleHeldThrough Context triple: [Lady Leila Primrose, nobleTitleHeldThrough, Primrose family]
-
A.
aristocraticTitleHeldTo
Indicates that one entity holds or bears an aristocratic or noble title in relation to another entity (such as a person, family, or jurisdiction).
-
B.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
-
C.
aristocraticTitleHeldFrom
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
D.
nobleTitleHolderInPeriod
Indicates that a person held a specific noble title during a specified time period.
-
E.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 11:37 p.m.