Triple
T3205670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wachtendonck Psalms |
E67154
|
entity |
| Predicate | originalManuscriptStatus |
P4091
|
FINISHED |
| Object | lost |
—
|
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: lost | Statement: [Wachtendonck Psalms, originalManuscriptStatus, lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalManuscriptStatus Context triple: [Wachtendonck Psalms, originalManuscriptStatus, lost]
-
A.
manuscriptStatus
Indicates the current state or phase of a manuscript within its creation, review, or publication process.
-
B.
originalTextStatus
chosen
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
C.
manuscript
Indicates that an entity is a written or typed document, often a draft or original version of a text, associated with another entity (such as its author, subject, or publication process).
-
D.
originalManuscriptLocation
Indicates the place where the original version of a manuscript is physically kept or stored.
-
E.
draftStatus
Indicates the current stage or condition of an item within a drafting or revision process (e.g., whether it is in draft, under review, or finalized).
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.