Triple
T14749132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary North |
E346556
|
entity |
| Predicate | formOfWorkAppearedIn |
P36545
|
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: [Mary North, formOfWorkAppearedIn, novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfWorkAppearedIn Context triple: [Mary North, formOfWorkAppearedIn, novel]
-
A.
formOfWork
chosen
Indicates that one creative work is a specific form, version, or expression of another related work.
-
B.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
C.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
-
D.
basedOnWorkAppearedIn
Indicates that something is derived from, adapted from, or otherwise created using a work that appeared in a specified source or publication.
-
E.
workWriterOfWorkAppearedIn
Indicates that a work is written by an author whose work appeared in a particular publication or context.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d2e1748190b16ede681fe52872 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.