Triple
T11437187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judge Rutherford |
E271039
|
entity |
| Predicate | reasonForTitleJudge |
P15925
|
FINISHED |
| Object | served as a substitute judge in Missouri |
—
|
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: served as a substitute judge in Missouri | Statement: [Judge Rutherford, reasonForTitleJudge, served as a substitute judge in Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTitleJudge Context triple: [Judge Rutherford, reasonForTitleJudge, served as a substitute judge in Missouri]
-
A.
reasonForTitle
chosen
Indicates the justification, cause, or basis for assigning a particular title to an entity.
-
B.
decidingFactorForTitle
Indicates that something serves as the key criterion or primary reason for determining or awarding a particular title.
-
C.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
D.
titleDeciderFor
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
E.
titleDecidedOn
Indicates that a final decision has been made regarding the title assigned to an entity or work.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088711ec8190afae9f4d9f2a11ca |
completed | April 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.