Triple
T38280448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Medicina |
E1022067
|
entity |
| Predicate | statusOfLargerWork |
P201632
|
FINISHED |
| Object | other parts 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: other parts lost | Statement: [De Medicina, statusOfLargerWork, other parts lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfLargerWork Context triple: [De Medicina, statusOfLargerWork, other parts lost]
-
A.
titleOfLargerWork
Indicates that one work is the larger or containing work (such as a book, journal, or collection) in which another, smaller work is included or published.
-
B.
creatorWorkPublicationStatus
Indicates the publication status of a work associated with a particular creator.
-
C.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
-
D.
ontologicalStatusInWork
Indicates the ontological status or mode of existence that an entity has within the context of a particular work (e.g., fictional, hypothetical, real-within-the-story).
-
E.
partOfLargerWorkByAuthor
Indicates that a work is a component or section of a larger work created by the same author.
- F. None of above. chosen
Provenance (4 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_6a000efdbe948190b4bfa9871aa1a7ee |
completed | May 10, 2026, 4:52 a.m. |
Created at: May 3, 2026, 4:30 p.m.