Triple
T25023178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Richmond and Gordon |
E626633
|
entity |
| Predicate | titleMergedFrom |
P88537
|
FINISHED |
| Object | Duke of Richmond |
—
|
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: Duke of Richmond | Statement: [Duke of Richmond and Gordon, titleMergedFrom, Duke of Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleMergedFrom Context triple: [Duke of Richmond and Gordon, titleMergedFrom, Duke of Richmond]
-
A.
titleDerivedFrom
Indicates that the title of one entity is obtained or adapted from another entity.
-
B.
titleCombinesWith
chosen
Indicates that one title can be merged or used together with another title to form a combined or composite title.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
usedTitleFrom
Indicates that one entity has employed or adopted the title originating from another entity.
-
E.
title
Indicates that one entity serves as the formal name or designation of another 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 6:07 a.m.