Triple
T32503450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagler, 1830 |
E830722
|
entity |
| Predicate | citesAuthor |
P109842
|
FINISHED |
| Object | Johann Georg Wagler |
—
|
NE NERFINISHED |
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: Johann Georg Wagler | Statement: [Wagler, 1830, citesAuthor, Johann Georg Wagler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citesAuthor Context triple: [Wagler, 1830, citesAuthor, Johann Georg Wagler]
-
A.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
-
B.
collectionPublicationAuthor
Indicates that an entity is the author responsible for the publication of a particular collection.
-
C.
hasDBLPAuthorId
Indicates that an entity is associated with a specific author identifier in the DBLP bibliographic database.
-
D.
keyPublicationAuthors
Indicates that the specified authors are the primary or most significant contributors associated with a key or central publication.
-
E.
usedAsAuthorCitationFor
chosen
Indicates that one entity is cited or referenced as the author in the bibliographic citation of another entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4493e10819096554382b9c7d337 |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.