Triple
T31080632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Julius Bernstein |
E792084
|
entity |
| Predicate | hasGoogleScholarId |
P128603
|
FINISHED |
| Object | Z9l9Ue4AAAAJ |
—
|
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: Z9l9Ue4AAAAJ | Statement: [Daniel Julius Bernstein, hasGoogleScholarId, Z9l9Ue4AAAAJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoogleScholarId Context triple: [Daniel Julius Bernstein, hasGoogleScholarId, Z9l9Ue4AAAAJ]
-
A.
hasGoogleScholarProfile
chosen
Indicates that an entity possesses a Google Scholar profile associated with it.
-
B.
hasDBLPAuthorId
Indicates that an entity is associated with a specific author identifier in the DBLP bibliographic database.
-
C.
hasORCID
Indicates that an entity is associated with a specific ORCID identifier, representing a unique researcher or contributor ID.
-
D.
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.
-
E.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 9:02 p.m.