Triple
T28826148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Denham |
E727909
|
entity |
| Predicate | relationshipToSirEdwardDenham |
P202464
|
FINISHED |
| Object | aunt by marriage |
—
|
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: aunt by marriage | Statement: [Lady Denham, relationshipToSirEdwardDenham, aunt by marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSirEdwardDenham Context triple: [Lady Denham, relationshipToSirEdwardDenham, aunt by marriage]
-
A.
relationshipToLordDarlington
Indicates the nature or type of connection, role, or association that one entity has with Lord Darlington.
-
B.
relationshipToEdwinDrood
Indicates the specific familial, social, or interpersonal connection that one entity has to Edwin Drood.
-
C.
relationshipTypeWithEdwardDouglas
Indicates the specific nature or category of relationship that an entity has with Edward Douglas.
-
D.
relationshipToEdwardBloom
Indicates the nature or type of connection an entity has to Edward Bloom, such as familial, social, or other relational ties.
-
E.
relationshipWithEdmund
Indicates that there exists some form of relationship or connection involving the entity Edmund.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
| PDg | Predicate description generation | batch_6a008297ad4c81909ee2e713d2c754d1 |
completed | May 10, 2026, 1:05 p.m. |
Created at: April 28, 2026, 6:36 a.m.