Triple
T2557811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil May Care |
E56768
|
entity |
| Predicate | writtenToMark |
P40443
|
FINISHED |
| Object | centenary of Ian Fleming's birth |
—
|
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: centenary of Ian Fleming's birth | Statement: [Devil May Care, writtenToMark, centenary of Ian Fleming's birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenToMark Context triple: [Devil May Care, writtenToMark, centenary of Ian Fleming's birth]
-
A.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
writtenAtLocation
Indicates that an act of writing occurred at a specific physical or geographical location.
- F. None of above. chosen
Provenance (4 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd35b216881908f4ef32d1c1e5080 |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.