Triple
T26870566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfield Sentry |
E676598
|
entity |
| Predicate | legalProceedingsVenue |
P50130
|
FINISHED |
| Object | New York courts |
—
|
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: New York courts | Statement: [Fairfield Sentry, legalProceedingsVenue, New York courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalProceedingsVenue Context triple: [Fairfield Sentry, legalProceedingsVenue, New York courts]
-
A.
courtLocation
chosen
Indicates the place or venue where a court proceeding or judicial action takes place.
-
B.
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.
-
C.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
D.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
E.
courthouseLocatedIn
Indicates that a courthouse is situated within or at a specific geographic or administrative location.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 5:32 a.m.