Triple
T19117720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerville |
E467948
|
entity |
| Predicate | introducedToScotlandBy |
P134493
|
FINISHED |
| Object | Norman settlers |
—
|
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: Norman settlers | Statement: [Somerville, introducedToScotlandBy, Norman settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToScotlandBy Context triple: [Somerville, introducedToScotlandBy, Norman settlers]
-
A.
introducedToEnglandBy
Indicates that one entity was responsible for bringing or first establishing another entity in England.
-
B.
broughtToBritainBy
Indicates that something or someone was transported or introduced into Britain by a particular agent or source.
-
C.
firstRuledScotlandFrom
Indicates the location or domain from which an entity first exercised ruling authority over Scotland.
-
D.
cultIntroducedBy
Indicates that a particular cult or religious practice was brought into a place, group, or culture through the agency or influence of a specific person or entity.
-
E.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e399a6d8819090a9501ff1637b9d |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.