Triple
T16969818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salisbury City Walls (remnants) |
E411636
|
entity |
| Predicate | usedToEnclose |
P15848
|
FINISHED |
| Object | medieval city of Salisbury |
—
|
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: medieval city of Salisbury | Statement: [Salisbury City Walls (remnants), usedToEnclose, medieval city of Salisbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToEnclose Context triple: [Salisbury City Walls (remnants), usedToEnclose, medieval city of Salisbury]
-
A.
hasEnclosures
chosen
Indicates that an entity possesses or contains one or more enclosing structures, spaces, or bounded areas associated with it.
-
B.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
C.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
D.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ac23a48190992fa125fceb1eb2 |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.