Triple
T26595415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benfleet |
E667476
|
entity |
| Predicate | wasVikingBaseBeforeBattle |
P160670
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Benfleet, wasVikingBaseBeforeBattle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasVikingBaseBeforeBattle Context triple: [Benfleet, wasVikingBaseBeforeBattle, true]
-
A.
approximateCasualtiesVikings
Indicates an estimated number of people killed, injured, or otherwise harmed in events involving Vikings.
-
B.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
C.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
D.
JórvíkIs
Indicates that one entity is identified as or equated with Jórvík (the historical name for York), expressing that they are the same place or concept.
-
E.
VikingName
Indicates that an entity bears or is identified by a name associated with Vikings.
- F. None of above. chosen
Provenance (4 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61528e2b88190a35896a563572146 |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 2:10 a.m.