Triple
T10273474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York city centre |
E240897
|
entity |
| Predicate | hasCityWallsLength |
P63706
|
FINISHED |
| Object | approximately 3.4 kilometres |
—
|
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: approximately 3.4 kilometres | Statement: [York city centre, hasCityWallsLength, approximately 3.4 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityWallsLength Context triple: [York city centre, hasCityWallsLength, approximately 3.4 kilometres]
-
A.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
B.
cityWallLength
chosen
Indicates the measured length or extent of a city's defensive wall.
-
C.
hasPeaceWalls
Indicates that there exist physical barriers or walls separating groups or areas to reduce or prevent conflict or violence between them.
-
D.
hasHistoricTownWallsRemnants
Indicates that remnants of historic town walls are present and associated with the subject entity.
-
E.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d288acf48190bbf14a5cb2dfe1f4 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:36 a.m.