Triple
T26423399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coppergate, York |
E664301
|
entity |
| Predicate | historicalCityNameContext |
P76172
|
FINISHED |
| Object | Jorvik (Viking York) |
—
|
NE NERFINISHED |
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: Jorvik (Viking York) | Statement: [Coppergate, York, historicalCityNameContext, Jorvik (Viking York)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCityNameContext Context triple: [Coppergate, York, historicalCityNameContext, Jorvik (Viking York)]
-
A.
historicalTownName
chosen
Indicates that the object is a former or historical name by which the town (subject) was previously known.
-
B.
historicalCityNameAtConstruction
Indicates the name a city had at the time a particular structure or construction was originally built.
-
C.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
D.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 26, 2026, 11:44 p.m.