Triple
T17093368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesicular stomatitis virus |
E414778
|
entity |
| Predicate | assemblySite |
P59462
|
FINISHED |
| Object | plasma membrane |
—
|
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: plasma membrane | Statement: [Vesicular stomatitis virus, assemblySite, plasma membrane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblySite Context triple: [Vesicular stomatitis virus, assemblySite, plasma membrane]
-
A.
locationOfAssembly
chosen
Indicates the place where a group, object, or structure is put together, constructed, or assembled.
-
B.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
-
C.
assemblyTerm
Indicates that an entity is associated with, or occurs during, a specific legislative or organizational assembly term.
-
D.
assemblyLinkedTo
Indicates that one assembly is associated or connected to another assembly in a meaningful or functionally relevant way.
-
E.
assemblyState
Indicates the current configuration or completeness status of an object or system in its assembly process.
- 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_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. |
Created at: April 10, 2026, 5:35 a.m.