Triple
T35475214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Norfolk Regiment |
E1025311
|
entity |
| Predicate | awardedHonoraryDistinction |
P173251
|
FINISHED |
| Object | Royal |
—
|
LITERAL FINISHED |
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: Royal | Statement: [Royal Norfolk Regiment, awardedHonoraryDistinction, Royal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedHonoraryDistinction Context triple: [Royal Norfolk Regiment, awardedHonoraryDistinction, Royal]
-
A.
honoraryDistinction
chosen
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.
-
B.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
C.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
D.
honoursAchievement
Indicates that one entity formally recognizes and celebrates the notable accomplishment or success of another entity.
-
E.
hasDistinction
Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:04 p.m.