Triple
T1906040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widow Douglas |
E38006
|
entity |
| Predicate | relationshipToMissWatson |
P33839
|
FINISHED |
| Object | sister |
—
|
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: sister | Statement: [Widow Douglas, relationshipToMissWatson, sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMissWatson Context triple: [Widow Douglas, relationshipToMissWatson, sister]
-
A.
relationshipToHuck
Indicates the specific type of personal or social relationship that one entity has with Huck.
-
B.
relationshipToHuckFinn
Indicates the specific type of personal or social relationship an entity has to Huck Finn.
-
C.
relationshipToAuntEller
Indicates the specific familial relationship that an entity has to Aunt Eller (e.g., whether and how they are related to her).
-
D.
auntOf
Indicates that one person is the aunt of another, typically as the sibling (or sibling-in-law) of a parent or sometimes an older female relative in an extended family role.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.