Triple
T14314810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquae Sulis |
E354927
|
entity |
| Predicate | presentDayUseOfSite |
P16008
|
FINISHED |
| Object | tourist attraction |
—
|
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: tourist attraction | Statement: [Aquae Sulis, presentDayUseOfSite, tourist attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayUseOfSite Context triple: [Aquae Sulis, presentDayUseOfSite, tourist attraction]
-
A.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
B.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
-
C.
presentDayAccess
Indicates that an entity currently has the ability or permission to access another entity or resource in the present day.
-
D.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
E.
modernArchaeologicalSite
Indicates that a location functions as an archaeological site characterized by modern-era remains, research, or excavation activities.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b49e5481909b9ffab2d922e284 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.