Triple
T34280713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York |
E879581
|
entity |
| Predicate | hadJusticeOf |
P179108
|
FINISHED |
| Object | New York Supreme Court |
E9467
|
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: New York Supreme Court | Statement: [New York, hadJusticeOf, New York Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJusticeOf Context triple: [New York, hadJusticeOf, New York Supreme Court]
-
A.
hasJustice
Indicates that an entity possesses, upholds, or embodies justice in its actions, qualities, or governing principles.
-
B.
hadJusticeOfHighestCourt
Indicates that an entity was served or presided over by a particular justice of the highest court.
-
C.
justified
Indicates that an action, belief, or decision is supported by sufficient reasons or evidence to be considered reasonable or warranted.
-
D.
seeksJusticeAgainst
Indicates that one entity actively pursues legal or moral accountability or retribution directed at another entity.
-
E.
hadStateJudge
Indicates that a particular state-level judge presided over, ruled on, or was otherwise officially responsible for a given legal case or judicial matter.
- F. None of above. chosen
Provenance (5 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e62c3c988190befdd735a7ae7ccc |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:57 a.m.