Triple
T7716616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CiteSeerX |
E174900
|
entity |
| Predicate | hasApproximatePublicationStart |
P78308
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [CiteSeerX, hasApproximatePublicationStart, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximatePublicationStart Context triple: [CiteSeerX, hasApproximatePublicationStart, 2008]
-
A.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
B.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
-
C.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
-
D.
epochAtPublication
Indicates the specific time or epoch at which the publication event occurs or is recorded.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702e9a32081909a153190a62af426 |
completed | March 27, 2026, 10:21 p.m. |
Created at: March 27, 2026, 4:05 p.m.