Triple
T34280731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York |
E879581
|
entity |
| Predicate | hasLocalCourts |
P20573
|
FINISHED |
| Object | City, Town, and Village Courts of New York |
—
|
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: City, Town, and Village Courts of New York | Statement: [New York, hasLocalCourts, City, Town, and Village Courts of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCourts Context triple: [New York, hasLocalCourts, City, Town, and Village Courts of New York]
-
A.
hasCourts
chosen
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
-
C.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
D.
hasCourtInEach
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
E.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:57 a.m.