Triple
T19168930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leukerbad |
E469260
|
entity |
| Predicate | usedSinceRomanTimes |
P72779
|
FINISHED |
| Object | for thermal baths |
—
|
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: for thermal baths | Statement: [Leukerbad, usedSinceRomanTimes, for thermal baths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSinceRomanTimes Context triple: [Leukerbad, usedSinceRomanTimes, for thermal baths]
-
A.
usedInRomanPeriodFor
chosen
Indicates that something served a particular function, purpose, or application during the Roman period.
-
B.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
C.
hasRomanRemains
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
D.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
E.
postRomanReuse
Indicates that something originally from the Roman period is used, repurposed, or incorporated again in a later, post-Roman context.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f162ac648190a5f60c6a77b68304 |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.