Triple
T24139271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Malloy |
E598178
|
entity |
| Predicate | placeOfLegalProceedings |
P50130
|
FINISHED |
| Object | Connecticut |
—
|
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: Connecticut | Statement: [William Malloy, placeOfLegalProceedings, Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfLegalProceedings Context triple: [William Malloy, placeOfLegalProceedings, Connecticut]
-
A.
courtLocation
chosen
Indicates the place or venue where a court proceeding or judicial action takes place.
-
B.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
C.
courtLocationTraditionallyIdentifiedWith
Indicates that a court’s location is customarily or historically recognized as being associated with a particular place, even if this identification is not formally or conclusively established.
-
D.
litigatesBefore
Indicates that a legal case or dispute is argued or conducted in front of a particular court or judicial body.
-
E.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e004fd38819080135a069e98a3e1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.