Triple
T4034574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sei Shōnagon |
E83795
|
entity |
| Predicate | workFeatures |
P34961
|
FINISHED |
| Object | lists |
—
|
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: lists | Statement: [Sei Shōnagon, workFeatures, lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFeatures Context triple: [Sei Shōnagon, workFeatures, lists]
-
A.
workFeatured
Indicates that one work is highlighted, showcased, or given special prominence within a particular context, collection, or presentation.
-
B.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
workDescribedAs
Indicates that one entity’s work, project, or output is characterized, labeled, or referred to by a particular description, title, or phrase.
-
E.
workAttribute
chosen
Indicates that a particular characteristic, quality, or property is associated with a specific work or piece of work.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb11d92481909aaebbc250ff45b9 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.