Triple
T21251552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Puttnam, Baron Puttnam |
E523755
|
entity |
| Predicate | created peer |
P41179
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [David Puttnam, Baron Puttnam, created peer, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: created peer Context triple: [David Puttnam, Baron Puttnam, created peer, 1997]
-
A.
createdPeer
chosen
Indicates that one entity brought another entity into existence or initiated its formation as a peer or counterpart.
-
B.
createdEarlBy
Indicates that an entity was granted or established as an earl by a specific creator or authority.
-
C.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
D.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
E.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359e90d881909b3153f1e7213c5c |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:57 p.m.