Triple
T38683544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Tunbridge Wells |
E949054
|
entity |
| Predicate | discoveryOfChalybeateSpring |
P174072
|
FINISHED |
| Object | early 17th century |
—
|
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: early 17th century | Statement: [Royal Tunbridge Wells, discoveryOfChalybeateSpring, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfChalybeateSpring Context triple: [Royal Tunbridge Wells, discoveryOfChalybeateSpring, early 17th century]
-
A.
thermalWaterDiscovered
chosen
Indicates that a source of thermal water has been found or identified, typically as a result of exploration or investigation.
-
B.
hasNumberOfMineralSprings
Indicates the relationship that specifies how many mineral springs are associated with a given entity.
-
C.
hasThermalBathsSince
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
-
D.
hasMineralSprings
Indicates that a place or entity possesses or is characterized by the presence of mineral springs.
-
E.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
- 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_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:33 p.m.