Triple
T33805607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Frayn bibliography |
E866377
|
entity |
| Predicate | includesNotableNovel |
P204258
|
FINISHED |
| Object | The Tin Men |
E246817
|
NE 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: The Tin Men | Statement: [Michael Frayn bibliography, includesNotableNovel, The Tin Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNotableNovel Context triple: [Michael Frayn bibliography, includesNotableNovel, The Tin Men]
-
A.
includesNotableNonFictionWork
Indicates that a collection, list, or body of work contains at least one notable non-fiction work as a member or component.
-
B.
hasNovella
Indicates that one entity possesses, includes, or is associated with a novella as part of its contents or attributes.
-
C.
hasNovelization
Indicates that a work has been adapted into a novel or prose narrative form.
-
D.
isOnlyNovelBy
Indicates that the referenced work is the sole novel created by the specified author or creator.
-
E.
hasNotableFable
Indicates that an entity is associated with a well-known or significant fable, either as its subject, source, or key element.
- F. None of above. chosen
Provenance (5 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36659b34c4819086e66a399e0fe25b |
completed | June 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
| PDg | Predicate description generation | batch_6a0358c89acc8190b22421ff8ce0f575 |
completed | May 12, 2026, 4:43 p.m. |
Created at: May 1, 2026, 1:46 a.m.