Triple
T201717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Tunbridge Wells |
E4519
|
entity |
| Predicate | grantedRoyalPrefix |
P917
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Royal Tunbridge Wells, grantedRoyalPrefix, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedRoyalPrefix Context triple: [Royal Tunbridge Wells, grantedRoyalPrefix, 1909]
-
A.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
B.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
C.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
D.
hasRoyalConnection
chosen
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
E.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.