Triple
T4724205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter, Paul and Mary |
E104840
|
entity |
| Predicate | disbandedAfterEvent |
P13662
|
FINISHED |
| Object | death of Mary Travers |
—
|
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: death of Mary Travers | Statement: [Peter, Paul and Mary, disbandedAfterEvent, death of Mary Travers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbandedAfterEvent Context triple: [Peter, Paul and Mary, disbandedAfterEvent, death of Mary Travers]
-
A.
disbandedByOrder
Indicates that an organization, group, or unit was formally dissolved as the result of an official order or directive.
-
B.
disbandmentYear
Indicates the year in which an organization, group, or entity formally ceased to exist or was dissolved.
-
C.
demolishedAfterEvent
Indicates that one entity (typically a structure) was demolished after the occurrence of a specified event.
-
D.
reasonForDisbandment
chosen
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
E.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.