Triple
T37994260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detta Walker |
E947901
|
entity |
| Predicate | hasMergedInto |
P102205
|
FINISHED |
| Object | Susannah Dean |
—
|
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: Susannah Dean | Statement: [Detta Walker, hasMergedInto, Susannah Dean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMergedInto Context triple: [Detta Walker, hasMergedInto, Susannah Dean]
-
A.
hasMerge
Indicates that one entity has been combined or integrated with another into a single, unified entity.
-
B.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
C.
laterMergedWith
chosen
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
D.
hasMergedTribe
Indicates that one tribe has combined or unified with another tribe to form a single merged group.
-
E.
someMembersMergedWith
Indicates that a subset of members from one group combined or integrated with members of another group to form a unified entity or subgroup.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.