Triple
T28704508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehnquist Court law clerks |
E729650
|
entity |
| Predicate | afterServicePath |
P169965
|
FINISHED |
| Object | legal academia |
—
|
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: legal academia | Statement: [Rehnquist Court law clerks, afterServicePath, legal academia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterServicePath Context triple: [Rehnquist Court law clerks, afterServicePath, legal academia]
-
A.
afterService
Indicates that one event, action, or state occurs subsequent to the completion of a specified service.
-
B.
laterServiceRoute
Indicates that one service route occurs after or succeeds another service route in time.
-
C.
resultingPath
Indicates the path or route that is produced as the outcome of a process, action, or decision.
-
D.
servedByServiceVia
Indicates that something receives service or is fulfilled through a specific service acting as the intermediary or delivery mechanism.
-
E.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 28, 2026, 5:44 a.m.