Triple
T4978760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Burial |
E111830
|
entity |
| Predicate | hasDialogueBetween |
P12142
|
FINISHED |
| Object | husband and wife |
—
|
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: husband and wife | Statement: [Home Burial, hasDialogueBetween, husband and wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialogueBetween Context triple: [Home Burial, hasDialogueBetween, husband and wife]
-
A.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
B.
dialogueType
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
-
C.
hasNoSpokenDialogue
Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
-
D.
numberOfDialogues
Indicates the total count of dialogues associated with or occurring between the referenced entities.
-
E.
dialogueWith
chosen
Indicates that two entities are engaged in a mutual conversational exchange or dialogue with each other.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.