Triple
T20893356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy Muriel Dundas |
E514463
|
entity |
| Predicate | spouse's instanceOf |
P123572
|
FINISHED |
| Object | human |
—
|
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: human | Statement: [Ivy Muriel Dundas, spouse's instanceOf, human]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouse's instanceOf Context triple: [Ivy Muriel Dundas, spouse's instanceOf, human]
-
A.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
B.
spouseOfInstanceOf
chosen
Indicates that one entity is the spouse of another entity that is an instance of a specified class or type.
-
C.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
D.
titleHolderSpouseInstanceOf
Indicates that the spouse of a title holder is an instance of a specified role, status, or class related to that title.
-
E.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05fecd88190905a0ea80a24406a |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.