Triple
T23553407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pantiles, Royal Tunbridge Wells |
E578114
|
entity |
| Predicate | typicalPeriodOfDevelopment |
P53998
|
FINISHED |
| Object | Georgian era |
—
|
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: Georgian era | Statement: [The Pantiles, Royal Tunbridge Wells, typicalPeriodOfDevelopment, Georgian era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPeriodOfDevelopment Context triple: [The Pantiles, Royal Tunbridge Wells, typicalPeriodOfDevelopment, Georgian era]
-
A.
eraOfPrimaryDevelopment
chosen
Indicates the time period during which something was primarily developed or formed.
-
B.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
timePeriodOfChildhood
Indicates the span of time during which an entity is considered to have been in its childhood phase.
-
D.
developmentalFor
Indicates that one entity serves as a developmental precursor, stage, or necessary condition for the emergence or maturation of another entity.
-
E.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed096b08190a8a755eaa7663fba |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.