Triple
T20994793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Darlington |
E517118
|
entity |
| Predicate | laterJudgedByStevens |
P142403
|
FINISHED |
| Object | as morally mistaken |
—
|
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: as morally mistaken | Statement: [Lord Darlington, laterJudgedByStevens, as morally mistaken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterJudgedByStevens Context triple: [Lord Darlington, laterJudgedByStevens, as morally mistaken]
-
A.
leadingJudgmentBy
Indicates a relationship where one judgment or legal decision is treated as the primary or authoritative basis guiding or influencing another judgment.
-
B.
chiefJusticeAtDecision
Indicates that the specified person was serving as the chief justice at the time a particular decision was made.
-
C.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
D.
laterCourt
Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
-
E.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
- F. None of above. chosen
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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1e75188190a97114238ea0b4f9 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:50 p.m.