Triple
T33601011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historiae Romanae |
E860719
|
entity |
| Predicate | hasScholarlyCommentary |
P124963
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Historiae Romanae, hasScholarlyCommentary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScholarlyCommentary Context triple: [Historiae Romanae, hasScholarlyCommentary, yes]
-
A.
hasScholarlyEdition
Indicates that an entity has an associated scholarly (critically edited and annotated) edition prepared according to academic standards.
-
B.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
C.
hasCommentaryIn
Indicates that an entity is discussed, analyzed, or annotated within a specific commentary work or source.
-
D.
hasScholarlyReception
chosen
Indicates that a work has been the subject of scholarly analysis, discussion, or evaluation in academic or research contexts.
-
E.
hasCommentaryForm
Indicates that one entity exists in, or is associated with, a commentary version or format of another entity.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:41 a.m.