Triple
T22969304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Albert’s Own |
E571135
|
entity |
| Predicate | hasHonoraryTitleType |
P94747
|
FINISHED |
| Object | royal association title |
—
|
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 association title | Statement: [Prince Albert’s Own, hasHonoraryTitleType, royal association title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonoraryTitleType Context triple: [Prince Albert’s Own, hasHonoraryTitleType, royal association title]
-
A.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
B.
hasHonorificType
chosen
Indicates that an entity is associated with a specific type or category of honorific title or form of address.
-
C.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
D.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
E.
hasHonoraryMember
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18231459881909dd25a0630c494d8 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.