Triple
T19215089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Pennsylvania Law Review |
E480460
|
entity |
| Predicate | typeOfArticlesPublished |
P218
|
FINISHED |
| Object | articles |
—
|
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: articles | Statement: [University of Pennsylvania Law Review, typeOfArticlesPublished, articles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfArticlesPublished Context triple: [University of Pennsylvania Law Review, typeOfArticlesPublished, articles]
-
A.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
B.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
hasNotablePublicationType
Indicates that an entity is associated with a publication of a specific notable type or category.
-
D.
publishedWorksBy
Indicates that one entity has created works that have been made publicly available by another entity (such as an author’s works published by a publisher).
-
E.
publicationTypeOfPresenter
Indicates the type or category of publication associated with a given presenter.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa397c188190b85bcfd9afd8dce6 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:22 p.m.