Triple
T30887937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 32nd Regiment of Foot |
E786817
|
entity |
| Predicate | honoraryTitleGranted |
P91035
|
FINISHED |
| Object | Duke of Cornwall's |
—
|
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 Cornwall's | Statement: [32nd Regiment of Foot, honoraryTitleGranted, Duke of Cornwall's]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoraryTitleGranted Context triple: [32nd Regiment of Foot, honoraryTitleGranted, Duke of Cornwall's]
-
A.
honoraryTitleGrantedTo
chosen
Indicates that an honorary title has been formally conferred upon a particular entity.
-
B.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
C.
nobleTitleGranted
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
D.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
-
E.
honoraryDistinction
Indicates that an entity has received a special honor, title, or distinction in recognition of merit, without necessarily conferring the usual formal status or responsibilities.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:49 p.m.