Triple
T34280730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York |
E879581
|
entity |
| Predicate | hasCountyLevelCourts |
P20573
|
FINISHED |
| Object | County Courts of New York |
E284809
|
NE 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: County Courts of New York | Statement: [New York, hasCountyLevelCourts, County Courts of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyLevelCourts Context triple: [New York, hasCountyLevelCourts, County Courts of New York]
-
A.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
-
B.
hasCountyLevelCity
Indicates that an entity (typically a region or province) includes or administers one or more cities that hold county-level administrative status.
-
C.
hasBranchCourts
Indicates that an institution or main court maintains one or more subordinate or satellite courts under its jurisdiction.
-
D.
hasCountyJudge
Indicates that a specified jurisdiction or administrative area is served or overseen by a particular county judge.
-
E.
hasCourts
chosen
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
- F. None of above.
Provenance (4 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e62c3c988190befdd735a7ae7ccc |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.