Triple
T1224236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalybeate Spring |
E26289
|
entity |
| Predicate | hasHistoricalEraOfPopularity |
P3813
|
FINISHED |
| Object | 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: 17th century | Statement: [Chalybeate Spring, hasHistoricalEraOfPopularity, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalEraOfPopularity Context triple: [Chalybeate Spring, hasHistoricalEraOfPopularity, 17th century]
-
A.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
B.
historicallyDominantIn
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
C.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
D.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
E.
popularInPeriod
chosen
Indicates that something is widely liked, used, or influential 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be233fd88190996faf4105c0b8d7 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.