Triple
T410034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Supreme Court |
E9467
|
entity |
| Predicate | judgesElectedFrom |
P4953
|
FINISHED |
| Object | judicial districts |
—
|
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: judicial districts | Statement: [New York Supreme Court, judgesElectedFrom, judicial districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgesElectedFrom Context triple: [New York Supreme Court, judgesElectedFrom, judicial districts]
-
A.
membersAreElectedIn
chosen
Indicates that the members of a group or body attain their positions through an election process held within a specified context or jurisdiction.
-
B.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
-
C.
judgesTerm
Indicates that one entity formally evaluates or makes a judgment about a specific term or expression.
-
D.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
E.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.