Triple
T33350150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Norfolk (The Tudors) |
E853911
|
entity |
| Predicate | familyAllegiance |
P114381
|
FINISHED |
| Object | Howard family |
—
|
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: Howard family | Statement: [Lord Norfolk (The Tudors), familyAllegiance, Howard family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyAllegiance Context triple: [Lord Norfolk (The Tudors), familyAllegiance, Howard family]
-
A.
fatherAllegiance
Indicates the allegiance or loyalty held by a person's father toward a particular group, cause, or authority.
-
B.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
C.
alliedFamily
Indicates that two families or family groups are connected through an alliance, cooperation, or mutual support relationship.
-
D.
associatedPoliticalFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular political family, dynasty, or lineage.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:34 a.m.