Triple
T29016752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Selig |
E737328
|
entity |
| Predicate | associatedWithWorkPublicationYear |
P69307
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [David Selig, associatedWithWorkPublicationYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWorkPublicationYear Context triple: [David Selig, associatedWithWorkPublicationYear, 1972]
-
A.
relatedWorkPublicationYear
chosen
Indicates the year in which a related work associated with the primary entity was published.
-
B.
authorWorkPublicationYear
Indicates the year in which a specific work created by an author was published.
-
C.
workPublicationEndYearContext
Indicates the year in which a work’s publication activity ended, along with contextual information qualifying or explaining that end year.
-
D.
partOfWorkPublicationYear
Indicates the year in which the larger work that this part belongs to was published.
-
E.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: April 28, 2026, 9:46 a.m.