Triple
T26171867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beorhtric of Wessex |
E654423
|
entity |
| Predicate | notableFeatureOfReign |
P8229
|
FINISHED |
| Object | Strong Mercian influence over Wessex |
—
|
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: Strong Mercian influence over Wessex | Statement: [Beorhtric of Wessex, notableFeatureOfReign, Strong Mercian influence over Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfReign Context triple: [Beorhtric of Wessex, notableFeatureOfReign, Strong Mercian influence over Wessex]
-
A.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
D.
notableFact
chosen
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
-
E.
sonNotableFor
Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 26, 2026, 8:35 p.m.