Triple
T2866667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton Legacy Library |
E63456
|
entity |
| Predicate | reissues |
P2247
|
FINISHED |
| Object | out-of-print titles |
—
|
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: out-of-print titles | Statement: [Princeton Legacy Library, reissues, out-of-print titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissues Context triple: [Princeton Legacy Library, reissues, out-of-print titles]
-
A.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
B.
wasReissued
chosen
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
C.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
D.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
E.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfbb7ed4819096ca65391077e2af |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.