Triple
T11648707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somnium Scipionis |
E276843
|
entity |
| Predicate | workNumberInDeRePublica |
P100178
|
FINISHED |
| Object | Book VI conclusion |
—
|
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: Book VI conclusion | Statement: [Somnium Scipionis, workNumberInDeRePublica, Book VI conclusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInDeRePublica Context triple: [Somnium Scipionis, workNumberInDeRePublica, Book VI conclusion]
-
A.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
B.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
C.
workNumberInSet
Indicates that a particular work number belongs to, or is included within, a specified set of work numbers.
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
laborNumber
Indicates a relationship where a specific labor or work assignment is identified or referenced by a unique number.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.