Triple
T38683555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Tunbridge Wells |
E949054
|
entity |
| Predicate | royalPrefixGrantedBy |
P8257
|
FINISHED |
| Object | Edward VII |
—
|
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: Edward VII | Statement: [Royal Tunbridge Wells, royalPrefixGrantedBy, Edward VII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalPrefixGrantedBy Context triple: [Royal Tunbridge Wells, royalPrefixGrantedBy, Edward VII]
-
A.
monarchGrantingRoyalPrefix
chosen
Indicates that a monarch has officially authorized the use of a royal prefix (such as "Royal") for a person, organization, title, or entity.
-
B.
dateGrantedTitleRoyal
Indicates the specific date on which a royal title was formally granted to an entity.
-
C.
monarchWhoGrantedTitle
Indicates the monarch who conferred or bestowed a particular title upon an individual.
-
D.
grantedRoyalPatronageBy
Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
-
E.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.