Triple
T26423420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jórvík |
E664302
|
entity |
| Predicate | derivedFromEarlierEnglishName |
P163059
|
FINISHED |
| Object | Eoforwic |
—
|
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: Eoforwic | Statement: [Jórvík, derivedFromEarlierEnglishName, Eoforwic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromEarlierEnglishName Context triple: [Jórvík, derivedFromEarlierEnglishName, Eoforwic]
-
A.
historicalNameInEnglish
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
-
B.
nameInOldEnglish
Indicates that an entity’s name is given or represented in the Old English language.
-
C.
hasLaterNameInEnglish
Indicates that an entity is known by a different English name at a later time or in a subsequent context.
-
D.
previousEraNameDerivedFrom
Indicates that the name of the current era is derived from, or based on, the name of a preceding era.
-
E.
historicalRegionNameDerivedFrom
Indicates that the name of a historical region is derived from, or based on, the name of another entity (such as a place, people, or feature).
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 26, 2026, 11:44 p.m.