Triple
T32375055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Chicago Law School Journals |
E827254
|
entity |
| Predicate | editorialWorkDoneBy |
P114311
|
FINISHED |
| Object | law students |
—
|
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: law students | Statement: [University of Chicago Law School Journals, editorialWorkDoneBy, law students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialWorkDoneBy Context triple: [University of Chicago Law School Journals, editorialWorkDoneBy, law students]
-
A.
editorOfWork
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
B.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
C.
wasEditorOf
Indicates that one entity served in the role of editor for another entity, such as a publication, work, or collection.
-
D.
hasEditorialWork
chosen
Indicates that one entity performs, contributes to, or is responsible for editorial work on another entity.
-
E.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:50 a.m.