Triple
T25260964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aglaia (almanac) |
E633301
|
entity |
| Predicate | hasWorkIncluded |
P12366
|
FINISHED |
| Object | works by Nikolai Karamzin |
—
|
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: works by Nikolai Karamzin | Statement: [Aglaia (almanac), hasWorkIncluded, works by Nikolai Karamzin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkIncluded Context triple: [Aglaia (almanac), hasWorkIncluded, works by Nikolai Karamzin]
-
A.
hasWorkBy
chosen
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
B.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
C.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
D.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
E.
hasWorkDetail
Indicates that an entity is associated with specific information or attributes about its work or job-related details.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 1:13 p.m.