Triple
T24958660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | healing complex of Epidaurus |
E624542
|
entity |
| Predicate | continuedInUseDuring |
P4341
|
FINISHED |
| Object | Roman period |
—
|
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: Roman period | Statement: [healing complex of Epidaurus, continuedInUseDuring, Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInUseDuring Context triple: [healing complex of Epidaurus, continuedInUseDuring, Roman period]
-
A.
continuouslyUsedAs
Indicates that one entity is persistently and repeatedly employed or utilized as another entity or for a particular function over an extended, uninterrupted period.
-
B.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
C.
maintainedDuring
Indicates that a certain condition, state, or relationship continues to hold throughout the duration of a specified event or time interval.
-
D.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
continuedInServiceOn
Indicates that an entity remained active, operational, or in use beyond a specified point in time or event.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:58 a.m.