Triple
T13009029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probate Division |
E322359
|
entity |
| Predicate | resolvesDisputes |
P6660
|
FINISHED |
| Object | contested wills |
—
|
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: contested wills | Statement: [Probate Division, resolvesDisputes, contested wills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvesDisputes Context triple: [Probate Division, resolvesDisputes, contested wills]
-
A.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
-
B.
resolvedDisputeOver
Indicates that one entity successfully settled or brought to an end a conflict, disagreement, or contention concerning another entity.
-
C.
handlesDisputesOver
chosen
Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
-
D.
numberOfDisputations
Indicates the quantity of disputations (formal debates or arguments) associated with an entity.
-
E.
disputeIssue
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9cf0108190b02f498c6ccc91f8 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:48 p.m.