Triple
T9587593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman city walls of Verulamium |
E231329
|
entity |
| Predicate | presentDayAccess |
P89957
|
FINISHED |
| Object | open to the public |
—
|
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: open to the public | Statement: [Roman city walls of Verulamium, presentDayAccess, open to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayAccess Context triple: [Roman city walls of Verulamium, presentDayAccess, open to the public]
-
A.
presentDayRemains
Indicates that something from the past still exists or has surviving traces in the present day.
-
B.
presentDayControl
Indicates that one entity currently holds authority, governance, or control over another entity in the present day.
-
C.
presentDayNear
Indicates that one entity is located a short distance from another in the present time or current context.
-
D.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
-
E.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99f01ca08190afaa44645a58e918 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:06 p.m.