Triple
T22895359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wales’s Own |
E568158
|
entity |
| Predicate | usedAsHonorarySuffixFor |
P341
|
FINISHED |
| Object | regimental titles |
—
|
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: regimental titles | Statement: [Prince of Wales’s Own, usedAsHonorarySuffixFor, regimental titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHonorarySuffixFor Context triple: [Prince of Wales’s Own, usedAsHonorarySuffixFor, regimental titles]
-
A.
honorificSuffix
chosen
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
B.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
-
C.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
D.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
E.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f17fc83d688190a8ab5ea0aad1e7ec |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.