Triple
T26659938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckstaff Bathhouse |
E666612
|
entity |
| Predicate | hasContinuousOperationSince |
P196355
|
FINISHED |
| Object | 1912 |
—
|
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: 1912 | Statement: [Buckstaff Bathhouse, hasContinuousOperationSince, 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuousOperationSince Context triple: [Buckstaff Bathhouse, hasContinuousOperationSince, 1912]
-
A.
isContinuously
Indicates that an action, state, or relationship persists without interruption over a period of time.
-
B.
endedContinuousControlSince
Indicates that an entity previously exercised continuous control over another entity or resource, but that control has ceased as of a specified point in time.
-
C.
hasContinuousVersion
Indicates that one entity is a continuous or uninterrupted form, edition, or variant of another entity.
-
D.
hasContinuousSequence
Indicates that there exists an unbroken, ordered sequence or range connecting the related entities without gaps.
-
E.
isContinuous
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
- F. None of above. chosen
Provenance (4 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: April 27, 2026, 2:36 a.m.