Triple
T17093369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesicular stomatitis virus |
E414778
|
entity |
| Predicate | budding |
P125880
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vesicular stomatitis virus, budding, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budding Context triple: [Vesicular stomatitis virus, budding, true]
-
A.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
B.
budbreak
Indicates the point in time or condition under which buds on a plant begin to open and resume active growth.
-
C.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
D.
bolting
Indicates that an entity is rapidly and suddenly moving away or fleeing from another entity or location.
-
E.
spurredGrowthOf
Indicates that one entity actively stimulated, accelerated, or caused an increase or expansion in another entity’s size, activity, or development.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfb89348190942984037bd3bd2e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.