Triple
T11218412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Aspern |
E265496
|
entity |
| Predicate | legacyForm |
P4181
|
FINISHED |
| Object | unpublished letters and papers |
—
|
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: unpublished letters and papers | Statement: [Jeffrey Aspern, legacyForm, unpublished letters and papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyForm Context triple: [Jeffrey Aspern, legacyForm, unpublished letters and papers]
-
A.
modernFormSince
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
B.
historicalForm
chosen
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
C.
legacyProject
Indicates that a project originates from an earlier phase, system, or generation and is being maintained or carried forward into the current context.
-
D.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
E.
standardModernForm
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ea19e8819095d5d02c1f145534 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.