Triple
T35077523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hardrada |
E1012344
|
entity |
| Predicate | dynastyMember |
P181976
|
FINISHED |
| Object | Harald Hardrada |
—
|
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: Harald Hardrada | Statement: [House of Hardrada, dynastyMember, Harald Hardrada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyMember Context triple: [House of Hardrada, dynastyMember, Harald Hardrada]
-
A.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
B.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
C.
dynastyInvolved
Indicates that a particular dynasty participates in, is associated with, or plays a role in the referenced event, process, or situation.
-
D.
dynastyFoundedByMember
Indicates that a dynasty was established or initiated by a specific individual who is a member of that dynasty.
-
E.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865d9dcc81909deaf635acd9ef56 |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f78418fdf0819090420479783c7d47 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78453e55c819091788e405261fc53 |
completed | May 3, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:01 p.m.