Triple
T33211590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jilly Cooper |
E850175
|
entity |
| Predicate | hasWrittenNonfictionOn |
P14097
|
FINISHED |
| Object | class in Britain |
—
|
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: class in Britain | Statement: [Jilly Cooper, hasWrittenNonfictionOn, class in Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenNonfictionOn Context triple: [Jilly Cooper, hasWrittenNonfictionOn, class in Britain]
-
A.
hasWrittenNonFiction
Indicates that a person is the author of one or more non-fiction works.
-
B.
hasWrittenAbout
chosen
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
C.
hasWrittenFiction
Indicates that one entity is the creator or author of fictional written works associated with another entity.
-
D.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
-
E.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.