Triple
T29088993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Letters of Dante Gabriel Rossetti |
E734202
|
entity |
| Predicate | hasFamilyMemberEditor |
P180870
|
FINISHED |
| Object | brother of Dante Gabriel Rossetti |
—
|
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: brother of Dante Gabriel Rossetti | Statement: [Family Letters of Dante Gabriel Rossetti, hasFamilyMemberEditor, brother of Dante Gabriel Rossetti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyMemberEditor Context triple: [Family Letters of Dante Gabriel Rossetti, hasFamilyMemberEditor, brother of Dante Gabriel Rossetti]
-
A.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
B.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
D.
hadMemberFamily
Indicates that an entity was a member of a particular family group during a specified time or context.
-
E.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 28, 2026, 11:03 a.m.