Triple
T9683562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Laird |
E234346
|
entity |
| Predicate | writesInStyle |
P89610
|
FINISHED |
| Object | contemporary literary fiction |
—
|
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: contemporary literary fiction | Statement: [Nick Laird, writesInStyle, contemporary literary fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesInStyle Context triple: [Nick Laird, writesInStyle, contemporary literary fiction]
-
A.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
C.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
writtenWithCharacter
Indicates that something is written using a particular character or set of characters as its writing system or notation.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccf21a08190a1302b933b9e50be |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:16 p.m.