Triple
T36293473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guliang Commentary |
E893294
|
entity |
| Predicate | laterPrintedIn |
P184029
|
FINISHED |
| Object | woodblock editions |
—
|
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: woodblock editions | Statement: [Guliang Commentary, laterPrintedIn, woodblock editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPrintedIn Context triple: [Guliang Commentary, laterPrintedIn, woodblock editions]
-
A.
hasBeenReprintedIn
chosen
Indicates that an item (such as a work or edition) has been published again in another source, format, or collection.
-
B.
printedInSeries
Indicates that a work was published as part of a particular series or serial publication.
-
C.
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.
-
D.
printsPublishedIn
Indicates that a print (such as an artwork or printed item) was published in a specific publication, venue, or medium.
-
E.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
Created at: May 3, 2026, 4:09 p.m.