Triple
T7912256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Friedrich Gmelin |
E183726
|
entity |
| Predicate | hasBibliographySection |
P45309
|
FINISHED |
| Object | zoology |
—
|
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: zoology | Statement: [Johann Friedrich Gmelin, hasBibliographySection, zoology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBibliographySection Context triple: [Johann Friedrich Gmelin, hasBibliographySection, zoology]
-
A.
hasBibliography
chosen
Indicates that one entity includes or is associated with a bibliography listing referenced or related works.
-
B.
hasBibliographicCategory
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
-
C.
hasGenreInBibliography
Indicates that a work’s bibliography includes sources belonging to a specified genre.
-
D.
followsInBibliography
Indicates that one bibliographic entry directly succeeds another in the ordering of a bibliography or reference list.
-
E.
hasFullCitation
Indicates that an entity is associated with a complete and properly formatted bibliographic reference.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.