Triple
T27930992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Murray, 2nd Earl of Mansfield |
E707979
|
entity |
| Predicate | nobleTitleLinkedTo |
P914
|
FINISHED |
| Object | Viscount Stormont |
—
|
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: Viscount Stormont | Statement: [David Murray, 2nd Earl of Mansfield, nobleTitleLinkedTo, Viscount Stormont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleLinkedTo Context triple: [David Murray, 2nd Earl of Mansfield, nobleTitleLinkedTo, Viscount Stormont]
-
A.
associatedNobleTitle
chosen
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
B.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
C.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
D.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
E.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 7:03 p.m.