Triple
T20633588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah H. Swayne |
E507017
|
entity |
| Predicate | nominatedAsJusticeIn |
P109075
|
FINISHED |
| Object | 1862 |
—
|
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: 1862 | Statement: [Noah H. Swayne, nominatedAsJusticeIn, 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominatedAsJusticeIn Context triple: [Noah H. Swayne, nominatedAsJusticeIn, 1862]
-
A.
nominatedAsAssociateJusticeOn
Indicates that an entity was formally selected or put forward to serve as an Associate Justice on a court or judicial body on a specific date or occasion.
-
B.
nominatedAsChiefJusticeOn
Indicates that an entity was formally selected or proposed to serve as Chief Justice on a specific date or occasion.
-
C.
nominatedToSupremeCourtBy
Indicates that one entity formally selected or put forward another entity as a candidate for a position on the Supreme Court.
-
D.
nominatedToCourt
chosen
Indicates that one entity has been formally proposed or selected for appointment to a judicial court position.
-
E.
nominatedToCourtOn
Indicates that an entity has been formally proposed or selected for appointment to a specific court on a particular date or occasion.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0d808c81908a60abd02a22ed92 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.