Triple
T33802513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Hornby bibliography |
E866265
|
entity |
| Predicate | includesScreenplay |
P204242
|
FINISHED |
| Object | An Education |
E246782
|
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: An Education | Statement: [Nick Hornby bibliography, includesScreenplay, An Education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesScreenplay Context triple: [Nick Hornby bibliography, includesScreenplay, An Education]
-
A.
screenplayRecord
Indicates that there exists a record or documentation associated with a particular screenplay, capturing information about its creation, version, or related details.
-
B.
screenplayWrittenIn
Indicates that a screenplay was written in a particular language, medium, or format.
-
C.
screenplayFeature
Indicates that one entity is a screenplay that serves as the primary feature or main written work associated with another entity, such as a film or production.
-
D.
screenplayType
Indicates the specific category or format of a screenplay associated with a work or production.
-
E.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
- 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_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366599883c8190a319dcf124bdf1b8 |
completed | June 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
| PDg | Predicate description generation | batch_6a03544190608190aa659147c9956a3c |
completed | May 12, 2026, 4:24 p.m. |
Created at: May 1, 2026, 1:46 a.m.