Triple
T34769157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment City |
E1002308
|
entity |
| Predicate | judgmentOutcomeOptions |
P151594
|
FINISHED |
| Object | moving on to a higher plane |
—
|
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: moving on to a higher plane | Statement: [Judgment City, judgmentOutcomeOptions, moving on to a higher plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgmentOutcomeOptions Context triple: [Judgment City, judgmentOutcomeOptions, moving on to a higher plane]
-
A.
judgmentResult
chosen
Indicates the outcome or decision produced by a judgment, such as a court ruling, evaluation, or formal assessment, regarding the entities involved.
-
B.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
C.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
D.
judgmentMessage
Indicates that a message expresses an evaluation, opinion, or decision about a subject or situation.
-
E.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.