Triple
T2161712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Journal of Law and the Arts |
E46814
|
entity |
| Predicate | editorialBoard |
P1392
|
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: [Columbia Journal of Law and the Arts, editorialBoard, law students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialBoard Context triple: [Columbia Journal of Law and the Arts, editorialBoard, law students]
-
A.
hasEditorialBoard
chosen
Indicates that an entity (such as a publication or journal) is overseen or governed by a specific editorial board.
-
B.
editorialManagement
Indicates the relationship in which one party oversees, coordinates, or directs the editorial processes, decisions, and content production of another.
-
C.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
D.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
-
E.
editorialControl
Indicates that one entity has the authority to direct, modify, or approve the content or presentation produced by another entity.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.