Triple
T29288410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Dundas of Arniston, the elder |
E742590
|
entity |
| Predicate | has honorific title |
P2097
|
FINISHED |
| Object | Lord Arniston |
—
|
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: Lord Arniston | Statement: [Robert Dundas of Arniston, the elder, has honorific title, Lord Arniston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has honorific title Context triple: [Robert Dundas of Arniston, the elder, has honorific title, Lord Arniston]
-
A.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
B.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
C.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
-
D.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
E.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653dada88190b0c075cca6a40536 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1 p.m.