Triple
T18255169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Ginsparg |
E437205
|
entity |
| Predicate | inceptionOfArXiv |
P42604
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Paul Ginsparg, inceptionOfArXiv, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfArXiv Context triple: [Paul Ginsparg, inceptionOfArXiv, 1991]
-
A.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
-
B.
firstPublicationPeriod
Indicates the time span during which something was first published or initially made publicly available.
-
C.
arxivId
Indicates that an entity (such as a paper or work) is associated with a specific arXiv identifier used to reference it in the arXiv repository.
-
D.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
E.
serialPublicationStartYear
chosen
Indicates the calendar year in which a serial publication (such as a journal, magazine, or series) first began being issued.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd84b3a481908bbc1a5e5034d397 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.