Triple
T35924248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.Juss. |
E1038974
|
entity |
| Predicate | belongsToAuthorSystem |
P200998
|
FINISHED |
| Object | botanical author abbreviations |
—
|
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: botanical author abbreviations | Statement: [A.Juss., belongsToAuthorSystem, botanical author abbreviations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAuthorSystem Context triple: [A.Juss., belongsToAuthorSystem, botanical author abbreviations]
-
A.
hasAuthorRoleFor
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
authorBelongsTo
Indicates that an author is affiliated with, or is a member of, a particular organization, group, or entity.
-
D.
hasAuthorType
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
E.
hasAuthorModel
Indicates that something is associated with or defined by a particular authoring model.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
| PDg | Predicate description generation | batch_69ffc082a4e881908a92313d2c755afe |
completed | May 9, 2026, 11:17 p.m. |
Created at: May 3, 2026, 4:07 p.m.