Triple
T26422951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Archaeological Trust |
E664289
|
entity |
| Predicate | createdAttraction |
P42853
|
FINISHED |
| Object | Jorvik Viking Centre |
—
|
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 Centre | Statement: [York Archaeological Trust, createdAttraction, Jorvik Viking Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAttraction Context triple: [York Archaeological Trust, createdAttraction, Jorvik Viking Centre]
-
A.
recordAttraction
Indicates that an instance of an attraction (e.g., interest or appeal) is documented or logged as a record in relation to another entity.
-
B.
notablePlaceCreated
Indicates that an entity is the creator or originator of a particular notable place or location.
-
C.
createdFeature
chosen
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
D.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
-
E.
openedAttraction
Indicates that an entity initiated the operation or public availability of an attraction at a specific time or event.
- 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 26, 2026, 11:44 p.m.