Triple
T12405263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Read |
E296367
|
entity |
| Predicate | activeAsWriterFrom |
P104966
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Miss Read, activeAsWriterFrom, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsWriterFrom Context triple: [Miss Read, activeAsWriterFrom, 1950s]
-
A.
primaryWriter
Indicates that one entity serves as the main or lead author responsible for creating or composing another entity.
-
B.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
-
C.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
D.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
E.
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.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e15f21c8190831c9562ffdd4fda |
completed | April 10, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:55 p.m.