Triple
T21807037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrey & A. Gray |
E538375
|
entity |
| Predicate | usedAsAuthorCitation |
P109842
|
FINISHED |
| Object | scientific plant names |
—
|
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: scientific plant names | Statement: [Torrey & A. Gray, usedAsAuthorCitation, scientific plant names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAuthorCitation Context triple: [Torrey & A. Gray, usedAsAuthorCitation, scientific plant names]
-
A.
usedAsAuthorCitationFor
chosen
Indicates that one entity is cited or referenced as the author in the bibliographic citation of another entity.
-
B.
usesCitation
Indicates that one entity supports or references its content by citing another entity as a source.
-
C.
usedByAuthor
Indicates that something (such as a method, tool, or resource) is employed or utilized by an author.
-
D.
isCitedFor
Indicates that one entity references another as a source of information, evidence, or authority for a specific claim, idea, or contribution.
-
E.
hasCitationRole
Indicates that an entity participates in a citation with a specific role or function (such as being the citing work, cited work, or contextual 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.