Triple
T31465623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Judge of the Employment Court |
E802712
|
entity |
| Predicate | appealLevelFrom |
P1031
|
FINISHED |
| Object | Employment Relations Authority decisions |
—
|
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: Employment Relations Authority decisions | Statement: [Chief Judge of the Employment Court, appealLevelFrom, Employment Relations Authority decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealLevelFrom Context triple: [Chief Judge of the Employment Court, appealLevelFrom, Employment Relations Authority decisions]
-
A.
levelOfAppeal
Indicates the degree or intensity to which something is attractive, interesting, or desirable to someone or something.
-
B.
appealsFrom
chosen
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
C.
appealBasis
Indicates the grounds, reasons, or legal basis on which an appeal is made.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
hadCourtLevel
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 30, 2026, 9:22 p.m.