Triple
T10426631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weymouth, Dorset, England |
E245804
|
entity |
| Predicate | hasProminentPeriodOfDevelopment |
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: [Weymouth, Dorset, England, hasProminentPeriodOfDevelopment, Georgian era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentPeriodOfDevelopment Context triple: [Weymouth, Dorset, England, hasProminentPeriodOfDevelopment, Georgian era]
-
A.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
B.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
C.
eraOfPrimaryDevelopment
chosen
Indicates the time period during which something was primarily developed or formed.
-
D.
hasCreativePeriod
Indicates that an entity is associated with a specific span of time during which it produced or engaged in notable creative work.
-
E.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea498ab08190b451c0b257c0711b |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.