Triple
T11212178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venta Belgarum |
E265334
|
entity |
| Predicate | hasCurrentSiteUse |
P16008
|
FINISHED |
| Object | urban area of Winchester |
—
|
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: urban area of Winchester | Statement: [Venta Belgarum, hasCurrentSiteUse, urban area of Winchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentSiteUse Context triple: [Venta Belgarum, hasCurrentSiteUse, urban area of Winchester]
-
A.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
B.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
C.
hasSiteStatus
Indicates the current operational or condition status assigned to a particular site.
-
D.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
E.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.