Triple
T735179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown design team |
E14913
|
entity |
| Predicate | workProduct |
P10663
|
FINISHED |
| Object | book covers |
—
|
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 covers | Statement: [Crown design team, workProduct, book covers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workProduct Context triple: [Crown design team, workProduct, book covers]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
workIncludes
chosen
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
C.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced entity.
-
D.
workRequirement
Indicates that one entity imposes or specifies a condition related to work that another entity must fulfill.
-
E.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.