Triple
T32539053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Obligations |
E831665
|
entity |
| Predicate | workNumberInCiceroCorpus |
P174566
|
FINISHED |
| Object | one of Cicero’s last philosophical works |
—
|
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: one of Cicero’s last philosophical works | Statement: [On Obligations, workNumberInCiceroCorpus, one of Cicero’s last philosophical works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInCiceroCorpus Context triple: [On Obligations, workNumberInCiceroCorpus, one of Cicero’s last philosophical works]
-
A.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
B.
numberInCorpus
Indicates the numerical count or frequency with which a given item appears within a specified corpus.
-
C.
numberOfWorks
Indicates the total count of works associated with a given entity.
-
D.
workNumberInCarminaBurana
Indicates that the entity is identified by a specific work number within the collection *Carmina Burana*.
-
E.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57bf54c819095f5f9fcd0cb966a |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.