Triple
T511563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton University Press |
E10620
|
entity |
| Predicate | publishingType |
P218
|
FINISHED |
| Object | scholarly books |
—
|
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: scholarly books | Statement: [Princeton University Press, publishingType, scholarly books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishingType Context triple: [Princeton University Press, publishingType, scholarly books]
-
A.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
B.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
D.
hasPublishingFormat
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f16768c081909d05537ff070868b |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edff001c81909182a7e26c6dc51b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.