Triple
T4881575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Moneypenny |
E109338
|
entity |
| Predicate | firstAppearanceWorkType |
P29367
|
FINISHED |
| Object | novel |
—
|
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: novel | Statement: [Miss Moneypenny, firstAppearanceWorkType, novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearanceWorkType Context triple: [Miss Moneypenny, firstAppearanceWorkType, novel]
-
A.
firstProductionType
Indicates the type or category of the initial production associated with an entity, such as its first manufacturing, creation, or release process.
-
B.
firstWork
Indicates that the related work is the earliest or initial work created, published, or produced by the entity in question.
-
C.
firstWorkInSeries
Indicates that a work is the initial installment or opening entry in a series or sequence of related works.
-
D.
firstPerformanceOfWorkAppearedIn
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
-
E.
firstAppearanceFor
chosen
Indicates that an entity marks the initial occurrence or debut of another entity within a given context 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dde6fcc8190a5aa7587f85632bd |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.