Triple
T7166489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juvenal |
E167080
|
entity |
| Predicate | workPreservedAs |
P21692
|
FINISHED |
| Object | manuscripts |
—
|
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: manuscripts | Statement: [Juvenal, workPreservedAs, manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPreservedAs Context triple: [Juvenal, workPreservedAs, manuscripts]
-
A.
workPreservedIn
chosen
Indicates that a work is maintained, stored, or archived within a particular medium, collection, or repository so that it remains accessible over time.
-
B.
workPreservationStatus
Indicates the current state or condition of efforts to preserve a particular work (such as whether it is preserved, partially preserved, or lost).
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
E.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85a07388190a07054ef12870fa1 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.